&gt; When I try to build something new, I find myself instantly criticizing my technique, to the point of paralysis. This function is hard to test; this object&#x27;s dependencies need to be injected rather than initialized internally; that module needs an integration test; and so on and so forth. Even when writing spike or proof of concept code, I find myself revisiting the same lines over and over again, looking for the best, most natural expression of the ideas it contains -- obsessing, like Catt said, over my own construct, rather than on the thing my code does.<p>I used to be like this for the first few years of programming.  And I knew a guy at my last job who was exactly like this.  The thing that helped me, when I felt the indecision paralysis come on, is to just do <i>something</i> and accept that it may be wrong.  You often don&#x27;t know the best decision in the first place because you lack experience.  Doing it the right way by accident, or making the mistake of picking the wrong way helps get you that experience.  Be deliberate about always doing something, and over time the paralysis will get less and less as you gain more experience.