Re:On code clarity: you can't be proud of something I can't ...
by cmpitg on Thursday July 02, 2015 @09:37AM
(#9818722)
I don't think it's fair to separate the code and the software itself. I personally don't feel proud of the result of a piece of software if the code is crappy, i.e. spaghetti code, (almost) unreadable, unmaintainable, ...
I think what the author wanted to emphasize was the importance of code clarity, as many of us developers don't actually care. Bad code builds up negative tech debts that somebody has to pay at some point in the future.
I'm not sure I've ever met a developer who is genuinely pleased with their code beyond a nice implementation of an algorithm or a neatly abstracted class. Most of us are deeply, sometimes overly, modest and humble about how readable our code is.