This is where my startup failed -- We made the decision to work in a new technology (then another!) but I was afraid of writing code I was less than proud of. I then proceeded to learn what I could of best practices, spending far too long experimenting with the language and far too little actually doing. In the end, we ended up with two half-baked infrastructures in two different languages and reached the trough of d…
The surprising thing I've found about being okay about sucking at writing is that often the "barf drafts" (as I call them) that seem god-awful when I'm actually writing them, turn out being pretty darn good when I revisit them.