viewI am an IT man by necessity, not by inclination. This is not a confession. It is a statement of fact, delivered without flourish and with no expectation of absolution. I did not arrive here through passion or destiny. I arrived because something failed, someone panicked, and I was inconveniently a competent champion. Competence, as it turns out, is not a talent so much as a trap. Once observed, it is relentlessly exploited.
So I stayed.
Let us dispense with pretence early. I loathe IT as a service. Not mildly. Not abstractly. I loathe it with the focused irritation one reserves for systems that actively discourage thought while congratulating themselves on efficiency. The queues, the scripts, the choreographed urgency that treats inconvenience as catastrophe and catastrophe as an opportunity for a dashboard refresh. I detest the language most of all. “Service delivery.” “Customer experience.” “Stakeholder satisfaction.” Phrases engineered to sound humane while ensuring nothing meaningful is ever discussed.
IT-as-a-service is not engineering. It is appeasement with credentials. The work is not to understand systems, but to reassure those who neither understand nor wish to. The goal is not improvement, but invisibility. Keep it running. Keep it smiling. Keep it sufficiently dull that nobody senior feels obliged to ask questions.
And yet.
Yet I love IT as a concept. Passionately. Nay, pervasively. Not the service catalogue, nor the performative empathy, but the idea itself. That logic can be formalised. That intent can be embedded. That we can design systems which remember what organisations forget and execute what committees eternally postpone. Technology, properly understood, is applied philosophy with teeth.
Which is precisely why organisations distrust it.
Modern institutions have learned to sedate technology by wrapping it in bureaucracy. Frameworks are applied not to guide thinking, but to pre-empt it. Governance becomes theatre. Compliance becomes camouflage. Responsibility is atomised until it can no longer be accused of anything in particular.
The resemblance to politics is neither subtle nor accidental.
In IT governance, as in government, decisions are made at a safe distance from consequence. Committees thrive where accountability would otherwise take root. Risk is not mitigated; it is processed, approved, and gently relocated. When failure arrives, as it always does, it is met not with curiosity but with choreography.
I have watched incidents unfold with all the gravitas of a parliamentary inquiry. Logs solemnly assembled. Timelines meticulously curated. Language scrubbed of agency. “Lessons learned,” we say, meaning lessons captured, archived, and carefully excluded from future behaviour. The objective is not to prevent recurrence, but to survive the narrative. A system that fails discreetly is infinitely preferable to one that succeeds disruptively.
Systems themselves, however, are not political animals.
They do not care for policy. They do not respect hierarchy. Under pressure, they abandon diplomacy and speak plainly. A race condition will reveal more truth than a shelf of strategy documents. A failed failover will confess assumptions that no one remembers authorising.
This is where my affection resides.
I build because building is unforgiving. You cannot consensus a dependency into existence. You must choose. You must compromise. You must accept that every design is an argument with reality, and reality is famously unimpressed by enthusiasm.
I break things for the same reason a musician practices scales. Not to destroy, but to understand form. To locate the tolerances. To identify which assumptions are structural and which are merely ceremonial. Breaking a system deliberately is not recklessness. It is a refusal to be surprised later.
Unsurprisingly, this disposition is poorly received.
IT-as-a-service treats curiosity as a compliance risk. Deviation as a governance issue. Standardisation is elevated to moral principle, even when it merely standardises incompetence. Variance is eliminated not because it is dangerous, but because it complicates reporting. Uniformity is mistaken for safety. Documentation for truth. Metrics for meaning.
And still, I love IT as a concept. Passionately. Nay, pervasively. Because beneath the laminated processes and colour-coded assurances, the ideas endure. Feedback loops. Failure domains. Emergent behaviour. Concepts that cannot be serviced, only understood. They belong to engineering, not customer success.
Music grasps this effortlessly. A good composition is disciplined insubordination. Structure exists to be tested. Rhythm exists to be played against. Jazz without discipline is chaos. Discipline without jazz is bureaucracy. Technology, regrettably, has embraced the latter and calls the resulting paralysis “maturity.”
The finest technologists I have known think like musicians, not administrators. They hear rhythm in traffic flows. They understand timing, pacing, and the value of silence. They know when to improvise and when to hold the line. They recognise that resilience is not rigidity, but responsiveness. That a system, like an ensemble, must listen to itself or eventually collapse under its own certainty.
So why remain?
Because necessity has a way of presenting itself as reason. Because bills are stubbornly unimpressed by ideology. Because proximity to systems still grants access to their truths. Because from inside the machinery one can observe how power avoids responsibility, how decisions are endlessly deferred, and how creativity survives in the margins not yet standardised out of existence.
I stay, but I am not invested.
This site exists for the same reason. Not to posture professionally. Not to optimise a brand. Not to dispense advice in exchange for attention. It exists as a place to think aloud without first seeking permission. To examine technology as a political system. To treat bureaucracy as a predictable failure mode. To use music as a reminder that order without imagination is merely control.
Here, I can say plainly that most innovation happens in spite of process, not because of it. That service models infantilise both provider and recipient. That compliance often replaces competence, and governance replaces responsibility.
And still, lest there be confusion, I love IT as a concept. Passionately. Nay, pervasively. Enough to criticise it without sentiment. Enough to resist what it has become. Enough to insist that understanding matters more than reassurance.
There will be more to say. About vendors who sell certainty they do not possess. About frameworks that confuse motion with progress. About incentives that reward obedience and quietly punish insight.
Consider this an opening statement.
The exposé will follow.