4 ms·
I experience this so often that I try to intentionally write software the first time with as little architecture as possible, so that there's less to strip out
by derefr 5y ago
I experience this so often that I try to intentionally write software the first time with as little architecture as possible, so that there's less to strip out when the "correct" architecture becomes clear. Just leave everything as a big bag of functions and mostly-unstructured values passed on the stack, until it's working. Then figure out what abstractions might help make the code more expressive.
- glouwbug 5y agoFunny enough, a big bag of functions and stack passed values is an accurate representation of assemble - how a computer might actually work. We often forget we're programming stack based machines
- andai 5y agoThis is also my approach to organizing my room: first I put everything on the floor. Once I can see it all at once, I see out how things relate to one another. I find it harder to see code all at once though (some IDEs have an "outline" of all variables and functions, but my current editor does not), and I wish there were more ergonomic ways to rearrange the order of things in code.
- smoe 5y agoThis approach has made my work much more relaxed and reduced stress a lot. The beauty of just first making it work somehow before going into design is that you can get rid of a good chunk of the unknown unknowns beforehand and you have a known working version you can always revert back to. It's less likely that you suddenly hit a brick wall when you think you are about to finish.