DEV Community

Cover image for Insights into a working day of a developer in a project
Julia 👩🏻‍💻 GDE
Julia 👩🏻‍💻 GDE

Posted on

Insights into a working day of a developer in a project

Today was my first day on the new project team. Although today's focus was on the setup, I already learned a lot of (useful) things and tools that I didn't know before. (I guess that's the great part of always working in other project teams).

Let me describe today in more detail 🤓

Daily Scrum Meeting
I attended the usual Daily for the first time today. The project has been going on for several months and I'm new to it (this is common, people coming and going during the project). All the devs talked about their issues and the latest status.

I had been assigned a mentor 🥰 with whom I set up my laptop. By the way, this is an additional laptop, there is an extra laptop for each project for security reasons. I was given all the access to the tools they use, Microsoft Teams, GitLab, etc.

New for me was that we work with Jira, an agile management tool, with Scrum board (there are also other boards like Kanban). There all current issues are entered in the Scrum Backlog, active ones were assigned to a Dev, in the Product Backlog you can find the whole list of all issues. Jira is a very clear and good tool to work effectively as a Scrum team.

As you can see, Scrum is very present, so I recommend you to get familiar with the framework before your first job. It will definitely come across well in the interview if you have already dealt with it.

Furthermore, we use Jenkins, also new for me, with which I guess you can build, deploy and automate the software. I haven't used it yet, so I don't know anything about it.

CMD Shortcuts
Shortcuts I learned today in the CMD 📝: when you type 'cd ', you can tab through all the existing folders in your current folder to select the one you want and don't have to remember exactly what the folders are called. And if you want to run an already executed command again, you can tab through all the previous commands and select the one needed with the up arrow key. Very handy, I wish I had known it earlier.

GitLens was also recommended to me to use. It is an extension in VSC that allows you to run git commands very quickly. It shows available branches, which one has merged into which one and much more. 😵 I have never seen so many branches in one project.... My issue has the number 875 😅

I also had to install NVM, a node version manager. I heard about it for the first time. We use it because webpack doesn't always have the same version in the different branches. And for everything to work, you have to select which node version you want to work with in each branch using e.g. nvm use 16.13.1.

Today was great. 🥳 I learned so many new things without writing a single line of code. I'm really looking forward to finally getting started with my issue.

Thank you

Thanks for your reading and time. I really appreciate it!

Top comments (1)

lunargravity profile image
Anu Altankhuyag

That sounds like such a fun productive day! Thank you for sharing your journey <3