Why being a lazy developer is not necessarily a bad thing | NetEngine

Why being a lazy developer is not necessarily a bad thing

Lucas Friday, 1 August 2014

A while ago I heard that being a lazy developer is not a bad thing. This could sound a bit weird to start with, but it makes a lot of sense. So, let me explain why you should strive to be a lazy developer and why it makes sense to hire one. Being a lazy developer means that you always try to avoid doing repetitive tasks and also don’t write code which will cause problems later.

Spending time doing lots of repetitive tasks isn’t only boring, but it can also lead to unneeded burnout. And then you will ask if there is a better way to do that. The answer is: yes, most of the time there is.

Basically the answer comes down to two words: automation and organisation. What do you and your team need to do is automate things through:

To automate repetitive tasks increases productivity, it dramatically reduces the possibility that mistakes happen and still gives you more time to invest in what really matters.

comments powered by Disqus