5.1 A Typical Day in the Life of a Developer
Being a programmer is easy and enjoyable. The Project Manager organizes the work, the Product Owner handles the product's feature list. Meetings are set up by the Scrum Master. All organizational processes are as formalized and standardized as possible.
You arrive at work in the morning, make yourself some tea or coffee, and sit down at your computer. You open the team chat, check if there are any urgent messages or if anyone is out sick, and if everything is OK, you get started with your work.
You open JIRA, where your team's task list is stored: the project backlog and the current sprint backlog. Tasks have already been sorted by priority by your Scrum Master/Team Lead or Product Owner.
You take the top task — the highest priority one and start working on it. You'll need to move it to the In Progress status, which takes just a couple of clicks. And that's it, the clock's ticking.
A task description usually includes additional info or a link to the documentation. The task should contain all the necessary information for you to complete it. Providing such info is your manager's job.
If something's off, you can reassign the task (or "task" in developer slang) to your manager and write in the comments what questions have arisen and/or what info is missing.
5.2 Writing Code
You've gone through the task description and you get what needs to be done. Awesome, get to it. Here, your experience from CodeGym and working in teams will come in handy.
Once the latest feature is ready, and you're sure of it, you need to push the code to Git. It's done with a couple of clicks directly from the IDE. In your case — from PyCharm. You commit your code first to your local repository and then push it to the central Git repository.
Most of the time, the last step is done via a Pull Request, where you use Git to send a request to your team lead for a code review. If everything's great with the code and there's no feedback, your team lead will accept your pull request, and it will be merged into the main working branch of Git.
Important! Never sit quietly if you don't know how to do a task. This situation happens often, and many newbies (and not just newbies) tend to handle it incorrectly. Remember, if after 2 hours you're still unsure of how to do the task, you need to let your manager know.
Also, don't approach the team lead with "this can't be done". Such a comment is quite annoying, especially if the team lead knows for sure that "it can be done", having done something similar multiple times themselves.
If you're stuck, say: "I spent two hours/two days trying to figure out how to do this, but I'm not getting anywhere." The team lead will guide you on which direction to Google.
So there you have a glimpse at the picture of modern product development. Writing code is just a small portion of the entire work, but everything is organized so that nothing distracts you from your task. So dive right into learning Python — you'll enjoy working as a programmer.
GO TO FULL VERSION