Our job is not to drink coffee and crap out code. Our job is to make software that works.
What a strawman. The article begins with a careful exposition about how the character can navigate the code with such ease because it’s so well written and follows by concluding that it’s important to serve customers, even if that means hacky code. How would this coder have been able to come up with this fix so efficiently if not for the careful, clean code? The kind of thinking espoused here is dangerous and belies the complexity of working in the real world. We live in a world of potentials, where we have to prioritize multiple customers’ needs over our own ability to deliver and have mental capacity left over. You don’t “serve a customer” by giving them a crappy hack. If you build to the implementation and not the interface, you will bury your maintenance developers and yourself. You have to put your own oxygen mask on first.