DevOps Zone is brought to you in partnership with:

After getting his master's degree in Software Technology, Sander became a software developer/architect specializing in Java and application integration. He loves sharing knowledge, for example through his blog and by writing for the Dutch Java Magazine. Sander speaks regularly at various international developer conferences, sharing his passion for Java, alternative JVM languages and related technologies. Sander is a DZone MVB and is not an employee of DZone and has posted 14 posts at DZone. You can read more from them at their website. View Full User Profile

Do You Recognize These Daily Developer Annoyances?

  • submit to reddit

I'm not complaining and I love my job, but sometimes...


You know it's a bad day when you experience all of these.

Exceptional errors

So you run into a really obscure error or exception. Google it. Result: many promising threads. Except you'll only find: 'I ran into this problem, help plz!' Bonus points for the sadistic 'never mind, solved it!' follow-up without an actual solution. Consider it a challenge.

Scratch this

Work on a feature all day long, only to discover that with a few lines of well-placed code somewhere else all your work is made redundant. Actually, this is enlightenment. But man, does it feel annoying.

Breaking bad

That awkward moment when you realize you pushed something completely unacceptable that will break the build.

Git woes

That awkward moment when you realize you forgot to push something completely acceptable that your co-worker needs.


Strange and hard to reproduce bugs happen. But often it's not you, it's them. Flippant browser caches. Unpredictable IDEs (I'm looking at you, Eclipse). Fumbling operating systems. Did you try refreshing/restarting/rebooting?

Coding, interrupted

Email. Twitter. Co-workers. Bosses. Recruiters. The first two are easily taken care of... yeah, right.

You start talking, I stop listening

"Can't we just ..." or, "how hard can it be?", or "it's just a small additional feature". Nope. Nip it in the bud, it only goes downhill from here. Skip the weasel words and have a realistic discussion, please.

Documentation fail

As in: no library documentation available. Or, if there is, it's wildly out-of-sync. Even worse: up-to-date auto-generated documentation. Come on library authors, documentation is the most important part of your API. We'll conveniently forget about the state of the documentation of our own code for now. No hard feelings.

Finally: I'm still not complaining, and I still love my job!

Published at DZone with permission of Sander Mak, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)