4 ms·
I try not to start writing code until I am at the point where it's pretty much just typing. It doesn't always work out this way, and it isn't necessarily always
by smhinsey 15y ago
I try not to start writing code until I am at the point where it's pretty much just typing. It doesn't always work out this way, and it isn't necessarily always the right move, but it forces me to have a really clear mental model of the problem in question before I start committing things to paper (so to speak), which typically saves a refactoring or two down the road.
- wccrawford 15y agoI usually end up doing a lot of the thinking about the problem while talking to whoever is requesting it. That's the only way to guide them to easier, cheaper, cleaner paths. There's still a lot of finer details to work through, but it's usually enough to get started coding.
- smhinsey 15y agoI do something similar. About 10 years ago or so I decided to force myself into writing the results of that sort of interaction down in a notebook, which forces me to rethink it as I convert it into user stories. This explicit step of recapitulating the same ideas repeatedly has had a lot of positive benefits for me.