Over a million developers have joined DZone.

Simplicity is Hard

DZone's Guide to

Simplicity is Hard

· DevOps Zone ·
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

Developers, in my experience, tend to be creative people and creative people can sometimes over complicate stuff. When a developer is struck by the lightning of inspiration the first thing that they usually want to do is start hammering the keyboard, spewing out the lines of code like it was going out of fashion. Now we all know you should plan you code and that there are methodologies for doing that, but that is a post for another day!

But even if you have a plan the code can still end up pretty damn complicated. And we all know that complexity means more bugs.

The answer to complexity? Refactoring. Even if you plan, it can still be very difficult to see which path leads out of the forest and which leads to the ginger bread house, and none of us want to end up there. It is not until we have the code in front of us that we can see where we can refactor and simplify.

This is why I think simplicity is hard. Most devs can knock out a code module or two. But it is the ones that go back and check their work and refactor through a number of cycles that make clean, elegant code which is simple.

Do you try and make your code simple? I would love to know so please leave a comment.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}