Pros and cons of each? Which do you prefer — fast iteration or thorough upfront design? Is one of these programming styles more effective in the long run?
I noticed two completely different ways of programming: 1. Write some small code, run, see the result, adjust, repeat for hours. 2. Sit for hours writing code, modelling with types, writing tests, then spend minutes fixing what you’ve got wrong. Turns out, this deeply influences the technology, programming languages and frameworks you prefer.

Jun 14, 2025 · 5:44 PM UTC

Replying to @DelyanRaychev
Ideally it will be a balance of both
1