carpenter 2,000 years a very good analogy with quality of code. This is very good reward system for developers . placing a premium on “skills learned or perfe

carpenter 2,000 years a very good analogy with quality of code. This is very good reward system for developers . placing a premium on “skills learned or perfected” over “bugs closed or features implemented” > We aren’t dealing with anything new in terms of work ethics and quality control in software development. I maintain my code quality the same way a carpenter 2,000 years ago would have cared about how well the insides of a finished product are designed, whether it exceeds its required specifications, what other carpenters would think of their work, how they would feel if a future apprentice or master saw what they created that day, and so on and so forth. > Additionally, I place a premium on “skills learned or perfected” over “bugs closed or features implemented.” If xx is better implemented via an approach I haven’t used before - well, here’s my chance to learn how to do that. Sure, it’ll delay the process. But that’s where technical debt comes from.