Over a million developers have joined DZone.

Why We Refactor

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

 Because we know what it is like to read and debug a 500-line method. And we don’t want to go through it again.

Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise.

Because we can’t think at the same time about both the solution and its readability. Even if we think we can.

Because there’s a good chance that our current design is not the best ever. Even if we think it is.

Because we want to decouple how we feel from what we write. Even if that elation of “I’m so close to pulling this off” is actually behind pulling it off.

Because we understand that our code has economic consequences for years to come. Even if we’re concentrating on solving that one bug that’s been haunting us for a week.

Because everything we write for the first time sucks. Even if it works.

Because we’re professional.

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.


Published at DZone with permission of Gil Zilberfeld, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}