Coding

14.1 A Typical Day in the Life of a Developer

Being a programmer is easy and enjoyable. The Project Manager takes care of the workflow organization, the Product Owner handles the product features list, and the Scrum Master arranges meetings. All organizational processes are as formalized and standardized as possible.

You arrive at work in the morning, brew some tea or coffee, and sit down at your computer. You open the group chat to see if there are any urgent messages or if someone is unwell, and if everything is okay, you start working.

You open the JIRA site, where your team's list of tasks is stored: the project's backlog and the current sprint backlog. Tasks are already prioritized by your Scrum Master/TeamLead or Product Owner.

You take the top task—the most important one—and start working on it. To do this, you need to change its status to In Progress. It's done with a couple of clicks. All set, time's ticking.

The task description usually includes additional information or a link to the documentation. The task should contain all the necessary information so you can execute it. Ensuring this information is present is your manager's responsibility.

If something's wrong, you can reassign the task to your manager and add comments about any questions or missing information.

14.2 Coding

You've studied the task description and know what needs to be done. Great, get to work. Here, your training on CodeGym and teamwork will help.

After another feature is ready, and you're sure about it, you need to upload your code to Git. It's done with a couple of clicks right from the IDE. In your case, from WebStorm. You commit your code first to your local repository, then push it to the central Git repository.

Most often, the last action is done through a Pull Request, where you use Git to request your team lead to review your code. If the code is good and there are no remarks, your team lead will accept your pull request, and it will be merged into the main working branch.

Also, don't go to the team lead with the phrase "it can't be done." This phrase can be very annoying, especially when the team lead knows for sure that "it can be done," and might have done something similar many times.

If you don't know how to do it, say: "I've spent two hours/two days trying to figure this out, but I'm not getting anywhere." The team lead will gladly point you in the right direction... for Googling.

So we've covered the picture of modern product development. Writing code is just a small part of the whole job, but everything is organized to keep distractions away from your work. So go ahead and dive into studying Frontend—you'll enjoy being a programmer.