Writing code

1. A typical day in a developer’s life

Being a programmer is easy and pleasant ☀️. Work organization is handled by the Project Manager, the product feature list is owned by the Product Owner. Meetings are run by the Scrum Master. All organizational processes are as formalized and standardized as possible ✅.

You come to work in the morning, make yourself some tea or coffee ☕️, sit down at your computer 🖥️. You open the team chat 💬, check whether there are any urgent messages, whether someone is sick 🤒, and if everything is OK, you get to work.

You open the JIRA site, which stores the list of all tasks for your team: the project backlog and the current sprint backlog. The tasks are already sorted by priority by your Scrum Master/Team Lead or Product Owner.

You take the task from the very top — the highest-priority one 🔝 — and start working on it. To do that, you need to move it to the In Progress status. This is done in a couple of clicks 🖱️. That’s it, the clock is ticking ⏳.

The task description usually includes additional information or a link to documentation 📄. A task should contain all the information you need to complete it. Making sure that information is there is your manager’s job 👨‍💼.

If something is off, you can reassign the task (“ticket,” in programmer slang) to your manager and write in the comments what questions came up and/or what information is missing.

2. Writing code

You’ve read the task description and it’s clear what needs to be done. Great, get to work 🏁. Your learning experience on JavaRush and your experience working in a team will help 🤝.

After the next feature is ready and you’ve verified it, you need to upload the code to Git. This is done in a couple of clicks right from the IDE. In your case — from GoLand🚀. You commit your code first to your local repository, and then you push (push) it to the central Git repository.

Most often, the last operation is done via a Pull Request, when you use Git to send a request to your team lead to review your code. If everything is great and there are no comments, your team lead will approve (accept) ✅ your pull request and it will land in the main working Git branch.

Important! Under no circumstances should you sit quietly if you don’t know how to do the task. This situation happens often, and many beginners (and not only beginners) handle it the wrong way. Remember: if after 2 hours you still haven’t figured out how to do the task, you need to notify your manager 🚩.

Also, you shouldn’t go to your team lead with the phrase “this can’t be done.” That phrase is very irritating, especially if the team lead knows for sure that “it can be done,” and has done something similar more than once.

Don’t know how to do it — say: “I spent two hours/two days trying to figure out how to do this, but I can’t make it work.” Your team lead will point you in the right direction for what to google 🔍.

And that’s a quick tour of what modern product development looks like. Writing code is only a small part of the job, but everything is organized so that nothing distracts you from your work. So go ahead and move on to learning Go 1.25 — you’ll enjoy working as a programmer 😉.