You might be wondering: why? Why spend countless hours building projects, learning new technologies, and documenting the journey? Why put yourself out there in this way?
The answer is simple, yet complex. It's about passion, purpose, and the relentless pursuit of growth.
Passion for Technology
I like this work more than is probably reasonable. Building a system, fixing a stubborn bug, watching an idea turn into something that runs: that part has never gotten old for me. Technology is a career, sure, but I would be doing some version of it anyway.
This site is a record of that. Each project here cost real hours of learning, debugging, and going back to fix what I got wrong the first time.
Continuous Learning
The industry moves fast, and what is current today can be dated in a year. The only answer I have found is to keep learning, and this site is where I write that down.
The HomeLab Kubernetes cluster taught me one set of things, working with AI and local LLMs taught me another. I build in order to understand how something works, not to have another repo.
The terminal look of this site is a nod to where most of my day happens. The command line is plain and does not hide anything, and I like that.
Building Real Solutions
I want to solve problems, not just write code. An online Python interpreter for learners, a text and image reverser, infrastructure that stays up: the point in each case was that someone could use it.
The HomeLab is not really about Kubernetes. It is about understanding distributed systems, networking, and security from the bottom up, on hardware I can break and fix myself.
Every project here had a purpose when I built it. Some were proofs of concept, some were practice, and a few led directly to bigger work.
Sharing Knowledge
I got most of what I know from other people's work: tutorials, documentation, open source, and strangers answering questions online. Publishing my own is the least I can do in return.
Maybe someone sees the HomeLab setup and builds their own. Maybe someone reads the code and picks something up. Either would be a good outcome.
It is also about being honest about the process. The debugging sessions and the "why isn't this working?" evenings are most of the job, and I would rather show that than a highlight reel.
The Future
AI is changing how we work, cloud infrastructure keeps getting more complicated, and security matters more every year. I want to be working on that, not watching it.
That is why my current focus is AI development, Kubernetes, and cybersecurity. I think those three will shape the next decade, and I would rather learn them by building now than catch up later.
This site will keep changing. New projects go in, old ones get updated or retired. It is a living document, not a snapshot.
The Bottom Line
I build because I enjoy it, because I want to keep learning, and because I want to work on real problems with real people using the result.
This portfolio is my resume, with the working parts left visible.
> Let's build something together.