7 classic problems of a programmer
Programming is not only work, hobbies, pleasure and warm-up of the brain, but also daily difficulties. Here are 7 side effects of unlimited love for the profession.
A typical office plankton problem is the consequences of sitting in front of a monitor. After 3-4 years, there are pains in the back, joints of the hands, dry eyes, loss of vision, and even headaches. After 10-15 years, they become chronic.
Solution . Simple prevention:
- every 30 minutes distract from the monitor and look around (not on the smartphone screen). 15-30 seconds is enough;
- take a walk around the office or home every 2 hours. Spend 2-3 minutes on your feet;
- every morning - exercise. Do you like to sleep? Then go to the gym after work: 3-4 trainings per week, one of which is gaming. Jogging in the evenings is another recipe for dealing with muscle and joint problems;
- follow the diet and drink 1 glass of water every 2-3 hours.
Lack of time
Sometimes strict time management acts to the detriment of the programmer. Here are a few causes of potential stress:
- own deadlines;
- deadlines set by the manager and customer;
- letters and questions requiring an urgent response;
- requests from colleagues for help;
- personal unresolved matters.
Some periods overlap with others, which creates a feeling of chronic lack of time.
Solution . Bad advice: sleep less and relax, better spend this time with "benefit".
Good advice: prioritize and grow thick skin. The manager asks to speed up the writing of the code? Calmly and reasonably explain to him that leaving you alone is the only way to do everything quickly and efficiently.
The pursuit of technology
The IT world is developing rapidly. What was studied last year is no longer relevant today. You need to constantly develop, keep abreast of the trends in your programming area. All this takes a lot of time and energy.
Solution . 3 easy ways to develop without problems:
- subscribe to news sites, podcasts, developer blogs. On the way to work, at lunch, in the free 15 minutes of a break, view them on your smartphone;
- Allocate 2–3 days a week for 2 hours for training. Strictly adhere to the schedule;
- Locate someone around you who can be interested in talking about programming. On Friday after working on hot tea, you will learn more than by reading dozens of guides and reviews.
There is nothing nicer than after a few weeks of work, pass the finished code. There is nothing worse than learning from the head that there are mistakes and inaccuracies in the code. On emotions, 2 decisions arise:
- To send a manager far away, accusing him of lack of professionalism, late reaction, inaccuracies in issuing TK.
- Erase everything and start writing code again.
Solution . If not only you are to blame for the errors, then clearly convey this to the leader. The main thing is not to overdo it. It’s very good that you are not indifferent to your code, but corrections are a natural part of the development process. Whoever makes a mistake, the code will still have to be fixed by you, so there’s no need to waste your nerves.
Reading someone else's code
You can’t avoid this either in the developer's place or in the manager’s chair. In your opinion, another’s code will always lack beauty, logic, simplicity, understandability, etc. As a rule, you don’t want to fix it; it’s more logical to write the entire block yourself. In fact, it takes a lot of time and effort, but does not always solve the problem.
Solution : everything comes with experience. And strong nerves.
Work for an idea
In mid-July, the media blew up the news: only 11% of workers receive cash compensation for their processing . Programmers are no exception. Employers use the enthusiasm of their subordinates, offering instead of a fixed overtime rate - one-time bonuses according to the results of the project (which may take months). Some go further, suggesting a rework for an idea and perspective.
Decision. A couple of hours a month is not scary, but you should not encourage systematic violations of TC. Do not fall for beautiful words, value yourself and personal time.
Any negotiations between the customer and the contractor are tiring. But if the former is far from a profession, as is often the case in programming, a headache cannot be avoided. But in addition to customers there are also:
- managers of different levels;
- colleagues with varying degrees of training;
- personnel from related areas.
To work calmly, you need to find a common language with all these people.
Decision. Once in a new place, chat without closing your mouth. Even if you are an introvert, overpower yourself for a couple of weeks. Ask personal questions, workers, feel free to disturb the little things. So you make contact with the environment. The only limitation is do not try to seem dumber than you are to start a conversation. It only spoils the attitude.
With customers and managers more difficult. The main argument in any contentious issues is a calm explanation of their position. This does not always help, but allows you to identify a tyrant, for conversations with which it is better not to waste time.
Daily problems are not much different from the tasks that you solve in your work. Like programming, the main thing here is not to lose your temper, not to complicate and choose the right tool.