Why not?

A realization came to me — an inkling of insight and inspiration of which I do not want to let go. It was spurred by a set of questions I was asked to answer recently, related to work/a job. The question, “How technical does a technical project manager need to be?” discussed in my previous post was one of them.

Here’s the deal, I should have done it 5 years ago, should have done it 20 years ago, but the best time to start something you haven’t started is … today. I am learning to code and I am starting with Python.

Motivation? A few things I know about what I want:

  • I thrive/work best, enjoy most a small, tight, collaborative, and trusting team — working on/producing something good — something that makes a difference.
  • I have been working as an application development manager for the past eight+ years, so I understand the language of software, and the process of development, and I have experience from years past with writing code — Thus my 0.1 starting point.
  • If flow/focus/lost track of time is an indicator of personal work enjoyment, as it is often said, then — though I have felt such in the graphic production of newspapers, I have felt it most, many, many years ago, in the writing and analysis of code.
  • I want work/a job/a means of revenue allowing a “walk-about” life-style. i.e. I don’t want to necessarily work in an office, I want to work wherever I want; I don’t want to work ‘for’ but rather ‘with;’ I want to serve / to assist in solving someone/some people’s problem.
  • In a word, I want “freedom”– and fulfillment … I guess that’s two words, but you get the picture!

I think I’ll write code.

And damn, did you know that Python is named after Monty Python? How can you argue with that??

Leave a Reply

Your email address will not be published. Required fields are marked *