Learning How to Learn How to Become a Programmer
An array of variables (programming pun intended), left me wanting to quit my job at the age of 32.
First, I didn’t love my job. I used to work in the international development sector in a generalist role. The job didn’t allow much space for creativity; the industry can be quite bureaucratic; the sector is exceptionally competitive and recruitment processes are slow, making it hard to switch organisation or role; my particular role was quite repetitive and only required a small set of soft skills (which became an issue when I started to look for other types of work). I’d also become cynical about the work that was being done. Enough said.
Second, my partner comes from Sweden, where we plan to eventually live. When I looked at the Swedish job market, I realised that my relatively limited set of soft skills would not cut it.
So, I started seeking an alternative career.
I outlined a list of needs and a list of wants. It needed to be: something that allowed me to work remotely (as my partner continues to work in the international development sector for now); something that would allow me to work in Sweden in the future; something in a growing sector so I would have a higher chance of getting hired at some point; something I could learn without going back to school at the age of 32. I wanted it to be something that would force me to develop some hard skills, something which I’ve always craved; something that would allow me to be creative; something that might eventually allow me to be my own boss and to work on my own projects.
After some months of background rumination, I decided on coding. (Or is it programming?) After carefully considering all of the above, this seemed to be the only option. This sounds limiting, but the beauty of it is that coding allows you to do so many different things.
So. Coding. Decision taken. Or so I thought.
Suddenly, the decision to learn to code, which had felt empowering and final, had shape-shifted into something paralysing and daunting.
That is what this series of entries will cover. The daunting and uncertain journey to becoming a coder (or a programmer?). It will touch on a whole range of topics. Choices that need to be made; mistakes I make along the way; great snippets of wisdom I stumble upon; useful resources that I find; summaries of what I have learned (in part to reinforce my own learning); and fears about whether or not learning to code was the right decision. It intends to be a resource for other people trying to navigate the same waters.
For now, I intend to simply set sail towards the open horizon with a big stock of patience and an abundance of curiosity (and this is what my advice would be to others who are seeking to transition into a coding career).
At this stage I first commit to learning, but not yet to any particular track, coding language, or specific end goal (other than eventually getting paid). Put another way, I intend to commit to be flexible and shift course along the way. The more I read about coding it seems to be a way of thinking and that once you learn one or two of the programming languages that are out there, you can more easily pick up the others. Relatedly, it also seems to be a sector that demands constant learning — somehow, this makes postponing a few decisions about exactly where to start and where to go a bit less scary.
Follow my journey in <The Self-Taught “Coder”> on Medium.