I am an engineer and writer interested in systems — human and machine — and how they interact. I build software and write about the things that interest me.
This page is an attempt to describe the person behind the site, the work I do, and how I think.
No description is equal in difficulty, or certainly in usefulness, to the description of oneself. One must spruce up, present oneself in an orderly arrangement, if one wants to go out in public. Well, I am constantly making myself presentable, for I am constantly describing myself.
— Michel de Montaigne, Essays, "Of Practice," Book II, Chapter 6
Difficult as it is to describe oneself, let me try.
I grew up in rural Zimbabwe, where I attended a Catholic high school. Later I attended the University of Zimbabwe, studying Mechanical Engineering. There, I was involved in student politics, and I started thinking seriously about how technology can be a tool for good.
After that I studied Electronic Engineering at the Harare Institute of Technology. I most enjoyed the courses on programming, microcontrollers, embedded systems, robotics, and artificial intelligence. I enjoyed the practical nature of the work, and learned to design systems from the ground up, with hardware constraints in mind.
I then worked as a Technical Writer for TalkJS, a Dutch startup, where I wrote documentation for their API and SDKs. At TalkJS I learned to work across teams, to think about user experience, and the value of good craftsmanship.
Since then I have been a software engineer working on web applications. I have worked on different projects, from websites to embedded systems to data collection and analysis tools. I have also worked on open source projects, including Matrix, Policy Engine, and the WHATWG HTML standard.
These three strands — engineering, technical writing, and open source — inform how I think and work. From engineering I have learned to think about systems, how they interact, and the constraints imposed on them by the external environment. Technical writing has taught me how to explain complex ideas clearly, and the importance of documentation and good communication. From open source I have learned the value of collaboration, transparency, and working on distributed teams. I have also learned a lot about development on large codebases, and how to contribute to projects I did not write.
These days I am moving that craft toward AI safety — compute governance, evaluations, forecasting, and the slower question of how people keep their agency as machines get capable. I have done several AI Safety courses (BlueDot: AI Alignment, AGI Strategy, ENAIS: AI Governance 101 & 201), and attended the ML4Good (technical track) bootcamp in 2026, and I maintain Africa Compute Tracker. I care about this partly because I write from a place that has already lived through several kinds of quiet disempowerment, and noticing early is a skill my country teaches.
Away from the screen: essays, history, the Zhuangzi, a morning jog, long quiet mornings. Montaigne asked que sais-je? — what do I know? — and I try to build and write in that spirit.
If you are here deciding whether to work with me, the test I would apply to myself has two halves: could I land a substantial change in a serious codebase I didn't write, and do I have considered thoughts on AI and the future? For the first, see my work — all of it real and inspectable. For the second, read the essays. And email reaches me quickly; I read everything.