Agreed. To make the best work you have to take pride in it. This work has my name on it, customers will use it, I want to improve their lives not make them wor

Agreed. To make the best work you have to take pride in it. This work has my name on it, customers will use it, I want to improve their lives not make them worse. The developers who come after me will need to assimilate this work. They'll need to build on it. I want to make their work a joy, not a burden. Do I take pride in what I do. It's not enough that the code just compiles. Pride is balanced by humility. I'm prepared to defend my choices (with well informed, well experienced) answers. But the choices I make are always a balance of upside and downside. And over my career things have changed which reweights some of those decisions. I'm open to external input from others because I want the result to be good not me to be right. I want to be proud of my work. But I'm humble enough to let others help me to improve it. [The above is my goal, sometimes I fall short]