A page about yourself is a strange thing to write. It is built to be a quiet brag, and I would rather it not be one, so here is the arrangement: I will brag a little, only where it is earned, and keep it in good taste. Everything after that is just true, written plainly.
My work is automation. AI agents that pick up the phone and hold a real conversation, multi-agent systems that pass a task between them until it is done, publishing pipelines, lead-generation engines wired straight into the tools a business already runs on. I am a verified creator on n8n. Most of what I build is invisible on purpose, the plumbing under the floor, so the thing you actually see just works, and keeps working while no one is watching it, sometimes for a full working day without a hand on it.
That kind of work teaches one habit above all the others. Automation is unforgiving. A wrong assumption does not announce itself. It sits quietly in the pipe and corrupts everything downstream, and you find it three steps too late, after it has already cost you something. So you learn to hold a precise model of how every piece behaves, and you learn to distrust anything you have not watched work with your own eyes.
I am entirely self-taught. No computer science degree, no bootcamp, no corporate training program. Just time, a low tolerance for not understanding something, and a refusal to stay where I started. That matters for everything that follows.
I knew the word long before I understood it
Quantum reached me long before I had any claim to it. It came through the television at dinner, while I ate with my parents and the news ran in the background, always in the voice the news keeps for things too large and too far away to touch. Quantum this, quantum that. To me it was not a subject. It was a sound from another world, one I quietly assumed I would never be let into, and I did not lose a moment of sleep over it. I had no reason to think any of it was meant for me.
Years went by. The word stayed exactly where it had always been, somewhere above my head, until one ordinary evening it did not.
The paragraph that would not let go
What finally pulled me back was a single paragraph about Grover's algorithm, and I could not put it down. I thought I knew what computation was. I had a clean model of it: a machine that checks one possibility, then the next, then the next, in order, until it lands on the answer.
Quantum took that model and broke it in the best possible way. There is a kind of computer that holds many possibilities at once and only commits to one when you force it to look. Not a faster version of the machine I knew. A different idea of what computing even is.
What hooked me was not the hype. It was the discomfort. I was holding a model I trusted, and it was wrong, and I could not stand not knowing why. That feeling, the itch of a broken model, is the thing I have chased my whole life.
The two halves of my head finally met
Here is the part I did not expect.
The strongest quantum algorithms running on real machines today are not pure quantum. They are hybrid. A quantum processor and a classical computer locked in a loop, passing the problem back and forth, each doing the part it is good at, until the answer settles. I have spent years wiring exactly that shape by hand, systems handing work to each other, none of them useful alone, the whole point living in how they connect. It was instantly familiar and completely new at the same time. That was the moment I knew this was not a passing interest.
Quantum is not a different career from the one I have. It is the same instinct, pointed at a stranger machine.
This is a notebook, not a tutorial
This is not a course, and I am not here to teach from a pedestal. It is a notebook, kept in public. A record of one person learning a genuinely hard thing from zero, in the open, getting it wrong first and then getting it right.
I write down the parts that bent my brain. The linear algebra I skipped in school and had to crawl back for. The Qiskit code that finally ran after an evening of failing at it. The moment a piece of math stopped being symbols and turned into something I could actually feel. I do not hide the gaps. The gaps are the most useful part of the whole thing, because someone a step behind me is stuck on the exact same one, and the honest version is the one that helps them.
Most quantum writing online is one of two kinds. Too shallow to be worth your time, or so deep it assumes a physics PhD you do not have. I am writing the one in between, the version I needed and could not find. Honest, technical, and built from scratch by someone who came in through the side door.
I run everything before I believe it
That same distrust came with me into quantum, and the field gives it plenty to do. A result I have only read about is not one I trust until I have run it myself and watched the numbers land the way the theory promised, or refuse to. For now, that means my own machine. The first run on real IBM Quantum hardware is a milestone I have not reached yet.
So the markers here are real and dated. Five IBM Quantum badges so far, every one with a date on it. It is not a highlight reel. It is a logbook.
Where this is going
I came from automation, and the bet I am making is a specific one. Right now you coax results out of a quantum processor mostly by hand. I think that changes. It becomes one more piece you wire into a system, a service you call, monitor, retry, and orchestrate, exactly the way I already wire everything else. The engineering around the machine, not only the physics inside it, is the part my background points straight at. It is the same job I have always done. This time the thing out front is a quantum processor. I cannot see the whole road. I can see the next step, so I take it, and the notebook gets one entry longer.
Where to find me
If you build things, break things, or simply refuse to stay at the surface of a hard one, you are in good company here. I keep my projects on GitHub, the ones running now and the ones still ahead. On LinkedIn I share what I am working on as it happens. Instagram and Facebook are where I am quickest to reach, the places I actually check and answer.