It’s difficult to know how to up-skill in the current era of programming. It seems like the advent of augmented coding (to steal a phrase from Kent Beck) has rendered a bit of analysis paralysis, at least personally. It’s extremely difficult to know what the future of programming is going to look like, and it feels like making an irrevocable bet on the future when choosing to dedicate months to learning something. I get it, and while I still don’t have a crystal ball into what the next 5 years of software look like, the clear wrong choice is to bury your head in the sand and do nothing. As the good Lord says in the book of Ecclesiastes:

“Do nothing without deliberation; and when you have acted, do not regret it.”

Since I cannot see what the next 5 years looks like, I will lean on a couple heuristics.

  1. Every time I have dedicated time to learning a technical engineering topic, I have come out a better engineer on the other side. Now it hasn’t always been immediately obvious when or how I will employ the new found learnings, but I always do. If anything, I find my ability to reason through problems, figure out the right level of abstraction, and develop good solutions gets better as a result.
  2. In a weird paradox, application code is becoming less important but also still matters. You still have to understand the application code to review it, and you probably won’t understand it well if you haven’t written it.
  3. Infrastructure, architecture, and security are becoming more and more important.
  4. I like hacking on stuff and find the infrastructure and security books exceptionally dry if not outright boring.

With this in mind, I am going to start learning about the following.

  • Learning Go: An Idiomatic Approach to Real-World Go Programming by Jon Bodner. This is so I can become a better programmer and developer and think differently about coding semantics. Eventually I am going to move on to C but not for a good while. The writings around this will be contrastive with Python.
  • Infrastructure as Code: Designing and Delivering Dynamic Systems for the Cloud Age by Kief Morris. This is to better understand infra, architecture, and security.

I also purchased an HP tower, and 2 old HP laptops (one that only has 1 GB of RAM) from an estate sale so I’ll probably have the odd project hacking around with those along with my Raspberry Pi.

Another thing, I just don’t have time to write like I used to after having kids. Not necessarily because my kids steal my time, but because I often would rather be hanging out with them. So my articles are going to be short sweet and to the point. If this interests you, please follow along!