#craftsmanship

I feel like it's been forever since I had a conversation about craftsmanship on the job. It's possible I have just found myself in the wrong places time and time again. Or maybe, and this is something I really fear, maybe the people who truly focus on the craft of software engineering are retiring or getting run off.

"In fact, I claim that if you don't take those rules to heart in your own source code then you are either unprofessional, lazy, not a team-player, or all of the above. If you as a software developer take pride in your professionalism and quality of your work then you have to consider that it is not only the achieved functionality for which you are being paid: The code you produce in almost all cases becomes property of your employer, and thus, the code itself also a product (and actually the most important product) you deliver. And how useful that code if for the team who has to work with it is what really determines its value."

"We should expect to learn. Sophisticated tools require study and effort, and they repay that effort by letting us do things we could not do otherwise"