On almost every team I've been on, I've argued for more time designing, refactoring, and writing tests (at the margin), but..
Every time I see a discussion on coding practices I wonder if writing "good" code is overratedpic.twitter.com/zEp6ZNXnqv
-
-
I think you need both. To iterate quickly and prove out an idea, “good” code may be overrated. Speed over Clarity
-
but for long term solutions, with large teams, you need cleaner code, good docs, good test cases its the only way to keep iterating
- 3 more replies
New conversation -
-
-
A lot of things matter more than code quality to a company's success. You only pay for bad quality when you are successful anyway.
-
That said, once successful, you might have to pay man-centuries fixing the bad practices, like using MongoDB as a queue.
End of conversation
New conversation -
-
-
Programmers solve problems. Minecraft was awful awful code but it was fun - and that beats a perfectly-coded unfun game every time.
-
(not saying refactoring/design/testing is useless but it needs to be in context of "How does this solve our customer's problems?")
End of conversation
New conversation -
-
-
Crafted code is rarely warranted in v1. Once it proves to be useful, the expected/desirable shelf-life and scale determines quality.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
See also Linley's Dungeon Crawl et seq.; the original code was famously bad, but the game was fun and acquired a following.
-
perhaps being a great coder is orthogonal to a variety of extremely important skills
End of conversation
New conversation -
-
-
overrated assumes professionalism is about success, but I think it's about pride in quality rather.
- 3 more replies
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.