{{ !articles[0].partner.isSponsoringArticle ? "Platinum" : "Portal" }} Partner

Why We Refactor

 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.

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

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

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks