3 ms·
Because what a "10x developer" (i would just call them pragmatic, personally) might call a shitty solution is still better than what you may call a well designe
by supermatt 7y ago
Because what a "10x developer" (i would just call them pragmatic, personally) might call a shitty solution is still better than what you may call a well designed testable solution?
Not everything needs 90% test coverage and more comments than code to be good. And not everything with 90% test coverage and more comments than code is any good at all.
- mamon 7y agoThis is so true, because people that are really good at something usually hold themselves to incredibly high standards (which is one of the main reasons they become master craftsmen in the first place).
- fogetti 7y agoYes. The standard is so high that they can't even find words for it. So they just call it simply shitty.
- deleted 7y ago[deleted]
- mugsie 7y agoNot at all. The quality of the code may be terrible. BUT - when someone else new comes along to look at it, the 90% code coverage, and comments helps them immensely - they can get up to speed to fix whatever bug has appeared a lot quicker.
- fogetti 7y agoPragmatism based on shittyism? Or how shall we imagine this? Is there a motto for this? "We excel in shitty code or something?"
- falcor84 7y agoI think it's just another variant of Less is More
- deleted 7y ago[deleted]
- supermatt 7y agoI think you are missing the point. That someone calls their own solution "shitty" doesn't mean that it's shitty by your standards, its shitty by theirs. The reality is that people have different standards. I don't understand the hate you seem to be exuding for productive people.