A Programmer?
The title itself made me laugh aloud.
For a long time, I could hardly bring myself to use the word programmer. It felt like a title reserved for people who had studied computer science, spent years writing software, or had been “tech people” all their lives.
Yet here I am.
Ironically, I never started this journey because I wanted to become a programmer. My curiosity began much earlier– with a simple desire to understand why text appears the way it does on a webpage. My love for literature, writing, and communication quietly led me into technology, and before I knew it, I had wandered into a world I once considered impossible to understand.
If someone had told me a few years ago that I would be writing Python code, debugging programs, or discussing dictionaries, sets, strings, and lists with genuine excitement, I would probably have laughed.
The Doubt
In fact, when I first shared my decision to learn programming, one of my childhood friends advised me to “examine myself” to be sure I wasn’t going crazy for attempting something like this at my age. I never took it as an insult. It came from a place of care. To him, programming belonged to younger people.
Perhaps, at the time, I believed that too.
But every passing day has quietly challenged that belief.
The Desire to Soldier on
Each lesson has become proof that the mind can keep expanding. Every concept I understand today is another small piece of evidence that growth compounds. I can now write simple programs, debug errors, explain ideas that once sounded like another language, and, more importantly, enjoy the process of learning.
Those may seem like small victories to an experienced developer.
To me, they are landmarks.
A New way of Thinking
The biggest surprise, however, has not been learning Python.
It has been discovering how Python has changed the way I think.
I no longer see problems as isolated events. Increasingly, I see them as systems made up of connected parts, each influencing the other. Files, folders, websites, spreadsheets, and even everyday tasks have started to look less like unrelated objects and more like information flowing through a process.
That has been one of the greatest gifts of this journey.
Programming, I have come to realise, is not merely about writing code.
It is about making decisions.
Every line of code is a decision based on the information available, the outcome you expect, and the relationship between one step and the next. Once I began to see programming this way, many things that had once felt confusing started making sense.
Practical Evidence
More surprisingly, this way of thinking has begun to influence areas of life far beyond Python.
It has made me more patient.
More observant.
More methodical.
It has trained me to concentrate for longer periods and to appreciate that meaningful results often emerge from many small, consistent improvements rather than dramatic breakthroughs.
Looking back, I no longer feel the need for permission or validation.
The results speak for themselves.
This season documents that transformation. But take aways from important parts of last season will continue showing up once in a while.
From where I am now, I see that it is no longer just about learning Python.
It is about learning to think differently.
And if there is one lesson I hope these pages communicate, it is this:
If the human mind can learn to see problems as systems, it can learn almost anything.
Welcome to Season Two.
This is where coding stopped being syntax and started becoming a way of thinking.
Tech Journey — Season 2, Episode 15.
Obi'sDeck 