What programmers hate

blog

"Hate is healthy," says researcher Julianne Holt-Lunstad from the University of Utah in Salt Lake City. Well, according to their investigations, it is better than ambivalent sensations, as these make the blood pressure rise the highest. With us you don't need to hold back your hatred. We don't want you to get sick!

 

So here: 10 things developers hate. Enjoy!

 

 

1) Program

 

Some things have to be loved in order to hate them. This kind of hatred we're talking about is something that developers are particularly familiar with. Programming is like having a girlfriend who will totally enrich your life. But she can also make it hell and you just don't know why. Apparently you're doing everything right and then, completely unexpected, she deletes your shared Facebook pictures and blocks you on Instagram. And vice versa, she bakes your favorite cake (Black Forest cherry, of course) after you've forgotten her mother's birthday ...

 

Confused? We also.

 

What we're trying to say: Sometimes the code just doesn't make sense. Everything seems to be right - error. You have no idea what you're actually doing - Success!

 

“Irony of a Dev's Life” - now on sale.

 

 

2) be interrupted

 

Emails, calls, meetings, a drone floating in front of your office window with a secret message: Oh yes, there are so many beautiful ways to be distracted. Especially in the century of the digital revolution. Slack can help, but it can also bring its own problems. Maybe you just want to be a good co-worker and feel compelled to respond right away, or you just can't stop adding your mustard everywhere. Once pulled out of the “flow”, it takes forever to get back to the topic.

 

 

Image credit: Geek's Humor

 

3) marketing

 

To the annoyance of the developer, there are situations in which marketing promises the customer heaven on earth. For example, to win them over or because they simply don't know that a product cannot have an infinite number of features. Sorry to all marketing professionals. We know there are real diamonds among you too!

 

 

4) Its old code

 

“Who was the idiot who wrote this terrible code ?! - Oh yes, that was me. ”. Seeing your own code after a long time can be almost as bad as working with another weak-matic kiss. The solution: write code as if whoever has to work with your code later is a psychopath and knows where you live. (Even if you are the psychopath!)

 

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Code for readability."

—John F. Woods

 

 


Image Credit: Reddit

 

 

5) semicolons

 

You have just written 1000 lines of code, now press the magic button and lo and behold: 1000 errors. Only the missing semicolon can be to blame for this. A semicolon that may seem so unimportant to others, but won't let you sleep for days.

 

 


 

6) Change of heart

 

"Totally cool, but I still have a few ideas that we should implement." No, just no. "It's nice that you were inspired during your yoga retreat, but that means that I can redesign the whole project," you might say to yourself. The customer is king and luckily we are no longer in the age of “Waterfall”, but let's be honest: short-term add-ons are just not fun.

 

 

7) Stereotype: Computer Doctor

 

Grandma, grandpa, uncle, aunt and the old lady from the neighboring village where your dog used to hide in elementary school. They all come to you as soon as they have any problems with their PC. We feel your sorrow. Maybe this shirt will help you.


 

  

Image credit: funny-tee-shirts.com

 

 

8) Stack overflow error

 

Okay, there's not much to say here. Just take a week off. You're excused!

 

 

9) Internet Explorer

 

Let's face it, the only thing Internet Explorer is good for is to download Google Chrome or Firefox. It is the tram among web browsers. You will surely agree with us when we say: “Ain't nobody got time for that!”.

 

 


Image credit: knowyourmeme.com

 

10) Recruiters

 

Recruiting can be a win-win-win situation for all parties. The company gets a new employee, you get a great job and the recruiter gets a few dollars and the satisfaction of having helped someone in their professional development. That is, you should be recruited by hy. But we know very well that most recruiters just don't care about you. They have no idea what you can do and what you want. It's like mass processing. But hey, should you ever come across a brilliant recruiter (such as our Ela), support them. Even if you are not looking for a job at the moment. Pass a friend on to him, keep an eye on him if you should look, or let me know if a position becomes vacant that might appeal to you. “You never know what you were missing till you try” as the good Emile Ford once sang.

 

And because devs have a lot more love in them besides all the hate, our next article is waiting for you soon: “10 things that developers love”. Stay tuned!