The 9 darkest nightmares of a programmer

Share:

 The 9 darkest nightmares of a programmer

 The 9 darkest nightmares of a programmer


Although Halloween only lasts one day, there are nightmares that recur throughout the year. If you dedicate yourself to the world of programming, surely there are scares, fears, or fears that you have to face on a daily basis.  The 9 darkest nightmares of a programmer
We can't prevent you from being afraid of ghosts, spiders, or spirits, but we can save you the odd headache and help you solve some of the nightmares that keep you awake.

The 9 darkest nightmares of a programmer ... what is yours?

1. Having to solve someone else's nightmare



You have just joined a new project, you have to continue with the work that another developer has started and, surprise! you have to decipher foreign lines of code or you find yourself with non-existent documentation. Does this situation sound familiar to you?

There are developers, as well as writers, who have their own coding style. Surely the next time you have to document your code (although doing so may be another nightmare) you will think twice. Be supportive!

 

2. Ask questions with ghost answers



When you have to solve a question or you are in trouble, the first thing that comes to mind is to ask the almighty Internet, it is impossible not to find an answer!

You enter forums like Stack Overflow or Github and find similar questions but with zero answers, or no one answers the one you ask. In these cases, remember that there was a time when the Internet did not exist, so you have to use your own logic and your experience.

3. Correct a mistake and show another 10



After typing hours and hours to solve an error in your code, you finally manage to solve it. Everything is a joy until you discover that another 10 new errors have appeared.

Do not panic! To prevent this nightmare you can use GIT, a version control software that allows you to go back to the previous registry before it attacks you.

4. Send information to the afterlife



No matter how skilled you are, losing information unexpectedly and wasting hours of work is a fear for most developers.

The code can disappear for various reasons: malicious bug hacks ... or simply because the files are not saved. To prevent greater evils, get in the habit of backing up every time you make significant changes.

5. Wasting time thinking about shrews



Our ability to concentrate is increasingly reduced and, in the face of the multitude of stimuli that surround us every day, it is very easy to get distracted and lose valuable time.

One way to be more productive is to use the Pomodoro technique: work in concentration periods of 20-25 minutes, and reward yourself with 5 of rest. Chrome extensions like Marinara allow you to put it into practice.

6. Be a technological mummy



In the IT sector, what was used 5 years ago may no longer be used or even worse! that neither exists. The speed with which technologies are updated is so high that it is easy to become obsolete.

In order not to fall into this nightmare, it is important that you learn to create your own continuous learning network. If, for example, you want to be up to date on which programming languages ​​are the most in-demand, you can consult the Tiobe Index, a reference index that is updated every month.

7. Explain your work to ordinary people



They say that programming is the new language of the 21st century. And of course, explaining to a colleague who is not immersed in the world of code what you do or why, can sometimes be frustrating.

Hence, it is important that, in addition to dedicating time to your technical training, you develop your soft skills: skills such as communication, empathy, or assertiveness, which will help you make yourself understood among mortals.

8. Become a zombie


Factors such as rush, stress, or the abundance of electronic devices, can make us forget that we not only work with a mind but also with a body.

If you don't want to end up turned into a zombie, it is important that you learn to manage your energy level, paying attention to the three levers of well-being: diet, physical activity, and rest.

9. Fall into the "burn out" syndrome


Every thinking mind needs to work on interesting and challenging projects to avoid falling into demotivation and reluctance, a syndrome known as "burn out."

We have the solution for it: take a look at our professional opportunities, and find projects with which to boost your career. 

Do you have any other nightmare as a programmer that you want to share with us? Leave it in the comments!

No comments

Note: Only a member of this blog may post a comment.