Hierarchy of any implementation: 1. Correct 2. Simple 3. Fast ------ Be wary of the temptation to flip 2 and 3. Fast is great but if you can never touch the code again what is the point?
I would make it simple before making it correct. Sometimes correctness can require handling a lot of edge cases and it can be better to take a step back first just in case there is another way forwards.
-
-
"Worse is better"
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.