Manufacturing design looks a lot like software: You iterate through possible solutions, and the manufacturing itself is about repeating the making process. But building software means learning about the problem as you solve parts of it. For that, you want flexibility. How do you find your ideal process?

If you accept that it’s OK to make the same mistakes over and over, you’ll never give yourself the opportunity to grow. If you don’t grow, you won’t improve your software. A writer should always ask why an editor did what he did, and a developer should understand how he can fix the code he broke.

Software testing tools can be incredibly helpful, but only if you're implementing them from a good starting place. If your code is a mess, a tool won't fix that; you'll end up simply adding layers on top of the mess. Matt Heusser explains how your team would be better off learning elements of code as craft.