3 ms·
The thing I find works better than anything else is to write some code that works, even though I know it's far from the "right" design. Once you have concrete
by BurningFrog 9y ago
The thing I find works better than anything else is to write some code that works, even though I know it's far from the "right" design.
Once you have concrete working code, it's much easier to organize it in ways that make sense than trying to visualize everything beforehand.
As a young programmer I was taught to carefully design code before starting to write it. It kinda blows my mind that now I design it after writing!
- stult 9y agoThat works for me too. I'm originally a lawyer and a decently competent writer and that's also how I approach papers or briefs. Writing is how I think and organize my thoughts so there's no more efficient way for me to design an overall architecture, whether in code or English, than just by starting to write. Once I start to get a grip on the parameters and pain points, I'll circle back and outline the higher level. My brain just works better from a bottom up starting point. Writing and coding are just formalized ways of thinking so sometimes you have to make concessions to your own brain's idiosyncrasies.
- convolvatron 9y agobottom-up is hardly a shameful idiosyncrasy. top down has a tendency to fail by imposing an inappropriate structure, and missing important details. every discussion i can remember ends up recommending switching directions repeatedly. i start on the up-stroke myself, always worked for me
- BurningFrog 9y agoYeah, I write a lot that way too, probably influenced by my programming habits. I read somewhere that Neil Gaiman considers himself only a decent writer who is an extremely good editor. Which is to say, he starts writing a simple draft, and then changes what's wrong with it, over and over.