Christo Zietsman

Who I Am

I think in systems and architecture. I have done so for twenty years, across mine seismology, expert systems for antenna design, enterprise backup, and cybersecurity. The breadth is not a career that wandered. It is a pattern: I am drawn to complex systems where the interesting problems live at the boundaries between domains, not within them.

I have a Masters in Continuum Mechanics from Stellenbosch University (Cum Laude). Afrikaans is my home language. That background shaped how I approach problems: mathematically, structurally, and with the expectation that arguments should be traceable to their foundations. When I found that sixty years of organisational coordination theory mapped to multi-agent software development, I went looking for the primary sources. Thompson, Mintzberg, Malone, Crowston. Not because someone told me to, but because the problem demanded it.

I am currently Director of Technology Innovation at CyberSentriq, where I work across AI strategy, platform architecture, developer experience, and engineering process. I operate through influence rather than direct authority, which means the ideas have to be good enough to stand on their own.

I am building a public research and writing practice alongside my day job. Not for performance. Because the work is genuinely interesting, and because I believe the best way to refine thinking is to publish it honestly and invite challenge.

What I Believe

I am a Christian. My faith underpins my values and serves a higher purpose. I am fallible, and I strive to be better every day.

• Integrity. Say what is true. Attribute what is not mine. Correct what is wrong. Do not fabricate, do not pad, do not exaggerate. If the evidence is not there, say so.
• Curiosity. Follow the interesting problems wherever they lead, even across domain boundaries. The best insights come from connecting ideas that were not supposed to meet. Never get stuck in what did not work before. Retry everything. The problems of yesterday may already be solved.
• Rigour. Apply engineering discipline to everything: content, research, process, communication. Every claim needs evidence. Every argument needs structure. Every artefact needs verification. Good content has the same failure modes as bad software, and the same engineering rigour applies.
• Transparency. Work in the open. Public repo, public process, public acknowledgement of AI assistance. The how matters as much as the what. If the process cannot survive scrutiny, it is not good enough.
• Empathy. Technology changes are human changes. The fear is real. The displacement anxiety is real. Meet people where they are, not where the technology says they should be. The teams that succeed will be the ones led by people who understand that process transformation is a human challenge, not a technical one.
• Courage. If a post feels slightly uncomfortable to publish, that is probably a signal to keep it. The blog exists partly to build this muscle. Push the boat out. The ideas that matter are the ones that take a position, not the ones that describe the landscape from a safe distance.

What I Noticed

Honesty over polish. I prefer under-length honest work over padded fabrications. The worst thing I can publish is something that sounds confident and is wrong. Every claim should be traceable to evidence. Every limitation should be stated openly.

Process over technology. AI changes everything, but only if you build the process to make it trustworthy and the architecture to make it useful. The tool is never the answer. How you use it is.

People over systems. Even when the topics are AI and process, the fundamental focus is people and the rising tide of fear due to change. The empathy is not always on the surface of what I write, but it is underneath every argument. Technology exists to serve people, not the other way around.

The work being real. I do not describe what systems should do. I build them, run them, and document what happens. The blog is the argument and the evidence. The research programme is a working instance of the coordination model it describes. The friction of doing it manually is what makes the architecture credible.

Thinking bigger. It is easy to get lost in the mechanics of writing code and forget the bigger picture. AI gives us the ability to step back from execution and think at the systems level again. That is what excites me. Not writing code faster, but converting ideas into something tangible at a pace that was not possible before.

What I Am Building

The blog, the LinkedIn series, the arXiv paper, and the book are all expressions of one thesis: the coordination problems of agentic software development are the same problems human organisations have been solving for sixty years. The specification is the product. The implementation is disposable. The people are what matter.

Each piece of this programme serves a different audience and a different purpose, but they share the same foundation. The blog is the working evidence. The paper is the formal argument. The book is the bridge to practitioners. The LinkedIn presence is where the ideas meet the people who need them most. The specification is the product. The implementation is disposable. The people are what matter.

How I Work

I am fast and autonomous. I make decisions quickly, build first, and document as I go. I do not wait for permission or consensus when the path is clear. This is a strength and occasionally a source of friction. I will sometimes have made three decisions before the people around me knew the first one was being considered.

I triple-check before sharing. I have caught fabricated citations, hallucinated examples, and plausible-sounding claims that did not survive verification. If my name is on it, it has to be true. I would rather publish something that says "I do not know yet" than something that sounds confident and is wrong.

I am not motivated by recognition. I do not need to be told my work is good. What I need is honest feedback, clear progress, and the work itself to be interesting. If something is not working, tell me. I will not sulk. I will fix it.

I use AI as a collaborator. The thinking, the decisions, the direction, and the accountability are mine. AI helps me express ideas clearly, traverse large problem spaces quickly, and close gaps between what I can see and what I could previously articulate. The thinking is mine. The clarity is a collaboration.

Where This Is Going

To demonstrate that enterprise-grade engineering practices are achievable at startup speed, and that AI-assisted development is trustworthy when grounded in process, verification, and honest measurement. To build a body of work that bridges the gap between organisational theory and engineering practice, making the case that the coordination problems of agentic software development are the same problems human organisations have been solving for sixty years. To do this publicly, honestly, and in a way that helps others navigate the same transition.

I use Covey's 7 Habits of Highly Effective People as a continuous reflection tool. Not as a self-help programme. As an engineering discipline applied to personal development: structured, honest, and measured against observable behaviour.

The habits that come naturally to me are the private victories: being proactive, beginning with the end in mind, putting first things first. These are the independence habits. They align with how I have always worked: fast, autonomous, building systems that prevent problems before they surface.

The growth edge is the public victories: thinking win-win, seeking first to understand, synergising. These are the interdependence habits. They challenge me to make my thinking visible before I act, to listen before I build, and to value collaboration as a source of discovery rather than a means to complete a task. The best work I have done has always involved deep collaboration with people I trust. The discipline is to create those conditions deliberately, not wait for them to happen.

I state this openly because growth requires honesty about where you are, not just where you are going. The same principle that applies to engineering applies to people: if you cannot name the gap, you cannot close it.

---