There Is No Bad Code

<p>They understand that it&rsquo;s not functionally doing what is expected, and so take the time to revise it until it&mdash;at least seemingly&mdash;does the right thing. If someone ever knows what it actually should do. When they do (think they) know, they might add tests, or even use a&nbsp;<em>test-driven approach</em>, to get to that state in which they have confidence that what is shipped is what is expected.</p> <p><strong>Some ship the code</strong>.</p> <p>They might know that it does the wrong thing. Maybe they hope no one will notice. Sometimes no one does.</p> <p><a href="https://medium.com/better-programming/there-is-no-bad-code-5198fb8a58c2"><strong>Read More</strong></a></p>