Well, let’s move on to your first day at a development company. Maybe you imagine coming to work, bringing your coffee mug (at least half a liter in size) in advance, brewing coffee and calmly starting to perform your duties. But such a plan of action is not entirely true. A programmer’s working day is divided into two stages: before launch and during project launch. Before launch – this is working in a regular mode at the office. Then dinner and another couple of hours I will “sit” from my home computer, because it was on the way home that a brilliant idea was born. The idea came up during dinner and now requires urgent implementation. The main thing here is to stop in time, because before you have time to blink an eye, it will be after midnight. The most disgusting thing is when you are trying to solve a difficult problem, but so far it has not been given. The task starts constantly spinning in my head: while eating, on the way to work, and even in my sleep. You need to relax, switch to something else, otherwise it will drive you crazy. Sports and yoga help a lot in such cases. As a rule, after rest and “distraction” the solution is found faster. In such a schedule there is always a “code hour”. Creative time, when all external communication channels are turned off and all my attention I turn only to programming.
A couple of “hacks” for efficient work:
- If you write down all tasks at once for an approximate date, the probability of forgetting is minimized, especially when there are a large number of projects and clients (these records must be transferred to the ‘to do list’).
- To make all the letters related to the task visible, it is convenient to use tags, for example ‘in progress’.
- Turn off the sound of mail notifications on your phone, so the flow of letters will not distract from your work with Java.
If we are talking about the actions that every beginner must perform in order to get respect from the whole team over time, then they are as follows. Try to make a positive impression on others. Politeness, courtesy, willingness to allegedly come to the rescue and sympathize. Feel the needs and concerns of the team. It is not worth rushing into battle, hoofing, demonstrating knowledge and enthusiasm. Try to “get into the rhythm” of the office atmosphere. Look, listen, be quiet and this will dull the vigilance of the team. At first, try to work as slowly and as little as possible, in case what is exactly required of you. You can justify yourself by saying that you need time to familiarize yourself. Then try not to work at all, but only to imitate the activity. But at first, you shouldn’t deal with personal matters. First, create a sense of your usefulness and hardness to replace. Coding and writing a project is also an important matter, but the main thing is the relationship between people in a team.