2 ms·
I do most of this, only I write tests too :) I tend to implement a rough version first, then write some tests, then get those tests working, then iterate and re
by marcus_holmes 12y ago
I do most of this, only I write tests too :) I tend to implement a rough version first, then write some tests, then get those tests working, then iterate and refine. Any time some code does something unexpected I write tests to define what I expect it to do and then get it to do that.
But Writing Code That Does Something is absolutely the important first step!
The other thing that I found helped get over this was to stop assuming that at some point some sneering jerk of a programmer would look at my code and criticise it for not using the latest shiny, and accept that the only time anyone would look at my code is if it became a success, and if that happened I could shrug off any criticism with a "it worked didn't it?" response. In other words, stop worrying what other people might think of my tech choices.