Technical systems, self-hosted infrastructure, APIs, automation, software, networking, security, experimental AI, and the occasional project that grows far beyond its original boundaries.
Not a résumé dump. These are projects that represent how I tend to work: build the underlying system, test it for real, then push it until it teaches me something.
A live FastAPI backend designed around AI-connected services, WebSockets, auth, databases, monitoring, Docker and MicroK8s. A custom GPT successfully called the backend through API actions.
React + Vite visual experiment intended as an interface layer for jc-web-api and a self-hosted AI logic system.
Archived pieces of a broader experiment in local AI behavior, response logic and system-controlled interactions.
Experiments around seeing what AI systems are actually doing instead of treating them as opaque magic.
Infrastructure, Django, React, networking, APIs, OpenAI tooling and assorted learning projects—some polished, some intentionally disposable.
The common thread is less “software developer” than systems curiosity: I want to know where the boundaries are, what breaks, and what happens when layers are connected in unusual ways.
This site is now also a record of the experiments that were worth remembering—not pretending every old project was complete, and not throwing away useful evidence because the larger goal moved on.
The repository that became this site was created while a broader web/API environment was being assembled.
The site became a status/documentation surface for a FastAPI backend exposed through personal domains and API documentation.
App Architect and Coder was configured to call the backend, while later frontend experiments explicitly referenced jc-web-api and the Sentient AI system.
Old systems are being inspected as evidence: identifying what actually worked, what was exploratory, and which ideas are still worth carrying forward.
I’m a hands-on technical builder. Documentation gives me the terrain; experimentation is how I actually learn it.
I tend to move between hardware, software, infrastructure, networking, security, APIs, automation and AI rather than staying inside one specialty. I’m especially interested in architecture, failure modes, unintended behavior, and the history hidden inside old systems.
This site is intentionally becoming less of a conventional portfolio and more of a living technical map: current work, recovered experiments, useful failures, and systems worth revisiting.