3 ms·
This has always been an issue with me. I first learned coding/programming in the days of "big iron," and embedded (machine and ASM) coding. These require a "M
by ChrisMarshallNY 4y ago
This has always been an issue with me.
I first learned coding/programming in the days of "big iron," and embedded (machine and ASM) coding.
These require a "Measure Twice, Cut Once" approach. In fact, the "coding" part is really just data entry.
These days, with integrated symbolic debuggers and IDEs, I can start coding right away, and writing a prototype is often MUCH faster than planning it out. I'll usually spend very little time, planning, and start coding, very quickly[0].
In the "days of yore," this would have me excommunicated.
But I have found that it results in extremely well-written, well-designed, and fast end results. I also tend to work very quickly.
Being experienced helps. In fact, it may be a requirement, as I can map out a design in my head that follows the desire path to a good result. I have very manageable failures, and seldom need to throw everything out, and start from scratch.
But even then, I'm not throwing out a whole boatload of invested time and effort. It's easy to toss a bad design, and that's critical, for me.
[0] https://littlegreenviper.com/miscellany/thats-not-what-ships-are-built-for/ https://littlegreenviper.com/miscellany/thats-not-what-ships...