4 ms·
Also the best way to write good software. First wrote bad code that works, then fix what's wrong with it.
by BurningFrog 4y ago
Also the best way to write good software.
First wrote bad code that works, then fix what's wrong with it.
- hvs 4y agoI agree. Especially when you don't really know how something is going to work. So many times when I'm working on a hard problem, coding out half a solution makes the rest of it naturally fall out (or show that I was completely wrong) without having to consciously think about it.
- dspillett 4y ago1. Make it work. 2. Make it work *right*. 3. Make it work fast. (4. Make it work right again…)
- BurningFrog 4y agoI put a "make it readable" step in there somewhere, but basically that's the cycle.
- hbrn 4y agoUnfortunately a lot of folks I met fall into this trap: I'm a senior engineer with XX years of experience, I cannot write bad code. Still haven't found a good way to convince them.