This is another tweet partially brought to you by Elephant in the Brain so h/t @robinhanson @KevinSimler. I'd actually love input on this one. Does this fit?
Providing higher quality code than necessary is an instance of the handicap principle in the software world. Basically, signaling you are skilled by doing your job in a more costly way. Examples: using strongly typed formal languages, extensive test coverage, hefty documentation
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Before someone trolls me: Yes, Rust can be good for some tasks (Mozilla created it for a reason), high test coverage makes sense sometimes (I just tweeted about it in fact), and documentation can be important. Still, many devs want these things more often than necessary
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This hinges on what you mean by necessary, so I suspect many instances of this are actually different estimations of "costly" (e.g. believing types/coverage/documentation actually save time). Related: I like Fowler's prudent/deliberate metricshttps://martinfowler.com/bliki/TechnicalDebtQuadrant.html …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.