Re:Visualizing How Developers Rate Their Own Programming Skills
by rhizome on Monday November 28, 2016 @03:06PM
(#13057950)
Does the choice have to be about the lowEST common denominator? Maybe a good criteria is to code for a lowER common denominator, just to account for the Bus Factor, maintainability, and so on. The lowest common denominator that makes sense, rather than playing denominator golf or disregarding the fact that you're coding for the benefit of your colleagues, too.
[ Parent
| on HN ]
Re:Visualizing How Developers Rate Their Own Programming Skills
by lacampbell on Tuesday November 29, 2016 @12:28PM
(#13064481)
I disagree. Rather than coding for the benefit of someone who doesn't know the language very well - people should learn the language. If the company is hiring maintenance programmers who don't know what lambdas are - again, their problem.
I feel like we should have higher standards, and use the abstractions available to us grow the code towards the problem. Instead I see people writing long sprawling application that use the same low level library routines everywhere.
Maybe it's a quantity vs quality thing. And quantity is much harder to hire for, so my ideas lose out.