he/him 
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?
-
Agree on flipping 2 and 3. However I always flip 1 and 2 which fits more into my work style.
No pointing building a complicated correct solution when a simple one would do the trick
-
-
Does "do the trick" mean tricking everyone that it's correct while in fact it's not entirely correct and will break later, on someone else's watch?
-
I've found that the definition of correctness tends to change with time as you dive deeper into a problem. Simple allows you to build up that early knowledge early on and incorporate it. It's also more flexible, allowing you to change course more easily than a "correct" solution.
- 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.