How should developers approach professional development?
There’s a joke that goes like this:
A doctor takes his Mercedes in for a brake job. When he picks up the vehicle the next day, the mechanic presents him with a bill for $2000. “Two thousand dollars for a brake job! I only charge $500 for a yearly checkup,” the doctor exclaims.
The mechanic replies: “Doc, you only have to work on two models. I have to work on a dozen and they change every year.”
Sound familiar? This is pretty much how it is in IT. We’re more like auto mechanics than doctors. We work on technologies that are constantly changing, and we need to keep up with it all. One unanticipated change can cause havoc.
Keeping up with technology
I know this from personal experience. Long story short, a bunch of Kubernetes deployments stopped working. An update in Kubernetes 1.9 changed the API group for deployments, which broke connections to old group IDs.
I am not alone.
So, how do developers keep up? We do professional development. (No pun intended.) What does it look like?
Read my insights on how to approach professional development for software developer and technologists.