Some people replying that simple should come before correct and I don't understand why you'd ever want something simple that didn't even work
https://twitter.com/samccone/status/1160660630631673856 …
-
Show this thread
-
Replying to @kentcdodds
It's easier to move from simple to correct, than complicated to correct. Therefore it's a better goal. Prioritising correctness can easily mean overcomplicating too early, and tying oneself in knots.
1 reply 0 retweets 1 like -
Replying to @sebinsua
And prioritizing simplicity can lead to premature abstraction which makes things overly complexhttp://kcd.im/aha
4 replies 1 retweet 13 likes -
Replying to @kentcdodds
I disagree with that because I don't think simple code is code has lots of abstractions. Simple code is easy to understand code, and the whole point of the phrase "simple, correct, fast: in that order" is that it is easier to achieve correctness with good understanding.
1 reply 0 retweets 0 likes
Basically, if your code is complicated, how can you really be sure that it is correct? See: https://news.ycombinator.com/item?id=17489934 …
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.