Do you care about your craft?
I’m reading through The Pragmatic Programmer again, this time stopping at each tip along the way and thinking about my work and how what the book is talking about applies to me.
The first tip is to “Care About Your Craft”
I had to realize that I haven’t really cared about the craft in some time. I’ve been sailing through a series of meetings, deadlines, changing project requirements, office politics and general life that the caring of the craft is at the bottom of my list of cares.
I used to care about the craft in detail: getting formatting in code right, following best practices, seeking the new more efficient way to do things. But now it’s just get it done and push onto the next thing.
Thankfully starting to do some summer technical book reading has ignited that care for craft in me again.
So I ask you all, do you care about your craft? Why or why not?
2 comments
[ 4.7 ms ] story [ 13.2 ms ] threadTo answer your question: I don't have the wherewithal to care at the moment, but I wish I did.
In some ways, that's passing the buck. I'm letting my employer determine my attitude about my work, which is probably unhealthy. On the other hand, caring about something when I'm not given the space to actually do what I feel needs done... that's pretty unhealthy, too. It can destroy you. So most of us respond by stopping caring, in self defense.
So, yes, that's kind of our fault. But it's also our employers. You want us to care about grinding out an endless stream of Jira tickets? Human nature says that won't happen.