Pragmatic Tip 1: Care About Your Craftposted in productivity on • by Wouter Van Schandevijl
“Why spend your life developing software unless you care about doing it well?”
— The Pragmatic Programmers
Yet Another Blog
Scott Hanselman said “Now, go write, create, commit.”. It took a while but here we are, blogging about “Programming and stuff”. I will be writing about languages and platforms I’m working on or learning about, solutions to problems I’ve struggled with and really any CS related topic I’m otherwise curious about.
The intention is to actively work and log on Andrew Hunt’s and Dave Thomas’ “Pragmatic Tips”, a set of 70 tips, each designed to help you become a better programmer as presented in their – already much appraised – book “The Pragmatic Programmer”.
Care About Your Craft
Their very first Pragmatic Tip “Care About Your Craft”” goes without saying. If you don’t enjoy communicating with the business (why put that first you ask…), trying to come up with solutions that work for both camps, if you don’t care about fighting code-rot and are not even trying to become a better professional but instead have to drag yourself to work each day to write code “by coincidence” only for that very same code to come back to haunt and derive you from your sleep during maintenance, then perhaps you should try to find something else? Why torment yourself like this when there are very likely jobs out there that you would in fact enjoy!?
In all professions, new things need to be learned as processes are refined or replaced, and this is especially true in our branch. You might currently be a specialist in a mainstream language such as Java or c# and while these won’t be outdated anytime soon, the keyword here should be “currently”. Like everything in IT, these languages will eventually disappear as newer and cooler languages are being introduced, languages that perhaps utilize a new programming paradigm that completely changes the way we think about code or languages that provide us a new level of abstraction enabling us to get things done faster with less and easier to understand code.
For those, like you and me, who care deeply about our craft these now-unattainable levels of boosted productivity sound attractive indeed even if it means having to learn a whole new paradigm. We’re more inclined to be happy about this turn of events: A whole new community opens up for which not yet any library or framework exists. Those who program only to pay the bills most likely don’t follow Pragmatic Tip 8: “Invest Regularly in Your Knowledge Portfolio”, and are slowly becoming obsolete as everyone and everything but them evolves.