As a former developer and manager, I'm here to address the grievances of backend developers.
When working at a startup, the CEOs often ask
"Is our team A working?" Backend developers especially receive such misunderstandings.
Unlike front-end development, where changes can be shown almost daily, backend development often takes several days.
Moreover, when writing reports, the content of yesterday, the day before yesterday, and today may be the same, and even if you ask, you might get the same report, "We are developing the sign-up feature," which leads to the misunderstanding of "Aren't you being insincere?"
In addition, even after development is complete, what can be shown is a DB query value or a JSON response value, and in many cases, it doesn't seem like a significant accomplishment.
The backend development becomes visible only after the front-end development is complete, but it looks like the front-end has done everything.
To eliminate misunderstandings and appeal that you are working smoothly, it would be effective to show it through Git work history.
<GitLab Commit log>
Or, it can be effective to show it by linking it to the tasks you have handled more easily.
Or, there is also a way to show the current development progress.
If you are curious about what backend developers do, ask them to show you through Git!
(I'll talk about the grievances of front-end developers soon!)