Comment Re:Opposite of Not Made Here (Score 1) 296
Nope. My commentary is that programmers are judged by the number of lines of code responsible for actual productive logic; and they are judged for that negatively.
If someone ever wrote something remotely similar, it is now your duty to incorporate their solution into your code, no matter how much of a square peg in a round hole it is. Glue logic, protocol translation, format conversions, abstraction layers, all that decorative code meant to link actual 'cores' of the system together, without doing anything productive, this is treated as something completely free - no matter how much of that you cram into your code, all is good. But if you're to perform an actual calculation, some real processing, the important stuff which transforms what is considered last stage of input into first stage of output, you'd better make sure it's not your code; that it's a library downloaded from a central hub, purchased, whatever. This is taboo, a thing you're not allowed to write yourself. Your code must adapt the raw input to what the library consumes, and what it produces into what the users receive.
The paradigm of not reinventing the wheel has been brought to illogical extreme. Even if you can cobble a fully working wheel together in 5 minutes, no, you must go through the process of creating the specs for the wheel, making a public offer for a supplier of precisely parametrized wheels with set warranty, establish the supply chain, and ordering the wheel from overseas. And then working out the kinks in all that.
It's not about the number of lines of code. It's about the culture that shuns "getting your hands dirty" and writing stuff yourself. And as result we're getting problems like the lpad fiasco, and hardware requirements endlessly climbing because the piece of code that actually does the work is wrapped in 30 abstraction layers that waste resources.