Coming into this module as a developer, my instinct was always to solve problems with more code. Give me a problem, and I’ll build you a solution. But eleven weeks of high-pressure hackathons, tutoring, and debates have completely rewired my definition of “innovation”, mostly by making me deeply uncomfortable.
I'll be honest...
I walked into this semester used to being the person in the room who people depended on and people just assumed I “know things.” Whether it’s the nuances of an ESP32 or the logic of a financial ledger, I’ve often found security in the fact that people trusted my knowledge enough to depend on me
This semester thoroughly challenged that ego.
In the trenches of our group sessions and hackathons, I suddenly found myself alongside people whose expertise made my technical skills feel almost redundant. If we already had a dedicated John Doe in this and a specialised Jane Doe in that, what was my role? It was an incredibly uncomfortable space to navigate.
At first, it felt like a total loss of utility. If I wasn’t the go-to ‘knowledge holder, what value was I actually bringing to the table?
What I learnt is that the “IS Professional” isn’t a solo hero, they are a synthesiser. I realised that the best systems don’t come from one person’s brilliance but from the friction of different perspectives. Learning to be a part of a high-performing machine, rather than the engine itself, was my most significant intellectual growth
Digital Stewardship
We talk a lot about innovation, but we don’t talk enough about maintenance. One of my biggest “lightbulb moments” this semester was realising that true ethical design is about sustainability.
The IS Procurement module only confirmed what my research in Bishop Lavis and Parow taught me. If a community can’t maintain the tech once the developer leaves, that isn’t progress. My role is to be a digital steward, choosing Human-Centred Design (HCD) over feature creep every single time.
This philosophy is already actively reshaping how I build. As I map out the user flows and cloud architecture for my personal projects, my newfound humility means I’m prioritising accessibility and the real-world constraints, building something I actually understand as opposed to building something like I’m marking items off a list just to keep up with the latest tech trend.
Fin...
On a personal level, this journey has been a bit of a mirror. As someone who identifies as an introvert, the collaborative intensity of this semester was a test. But I’ve found that being the “quiet one” in a team is actually a strategic advantage in IS. It allows for better listening, more thoughtful synthesis, and a focus on what the user actually said, rather than what we think they want. A message drilled into me since my very first year at UWC.
Song of the Semester:
Following my “Song of the Week” ritual, this final entry feels like a track that finally hits its crescendo. I walked into IFS740 wanting to learn how to build better software, but I’m walking out wanting to build better systems. The journey from a timid first-year at UWC to a digital steward hasn’t been comfortable, but it has been necessary. I used to assume the role of the engine, I wanted to be it, I needed to be it. Now, I’m perfectly content being the synthesiser.
I am walking away with a “triple-threat” perspective: the logic of an accountant, the grit of a developer, and the newly found humility of an IS strategist. The goal was never just to pass a module, it was to figure out how to use tech to actually move the needle in the South African context. I think I’m finally starting to hear the melody.
