Background
About
The human story behind the system.
I'm Chris Bruno. Self-taught. No CS degree, no FAANG internship, no bootcamp credential to lean on. What I have is a production system with 36 containers, 227 migrations, 1,593 tests, and 1,300+ commits, largely in collaboration with AI tooling.
The absence of a traditional background is the point. I learned infrastructure by building infrastructure. I learned database design by designing databases that broke and then fixing them. I learned AI orchestration by building an orchestration system that had to work in production, not just in a demo.
What "self-taught" actually means
It means you develop opinions. Not theoretical opinions from textbooks, but operational opinions
earned by watching things fail. The database has five roles because I once had a system where
everything connected as the superuser, and I understand exactly what can go wrong from that.
The migration system is tracked in a schema_migrations table because I've seen
what happens when you lose track of what's been applied.
It means the documentation is thorough, because the only way to remember why you made a decision three months ago is to write it down at the time. There are design documents, post-mortems, and architectural decision records for most of the major choices in this system.
ADHD as infrastructure
Neurodivergence plus the right tools produces a specific kind of output: deep focus on problems that are genuinely interesting, with AI systems handling the coordination and context management that ADHD makes difficult. The Director Model I built for multi-agent orchestration is, in part, a system for externalizing the executive function that doesn't come naturally.
The result is a system that reflects how I actually think: in parallel, across multiple concerns simultaneously, with an emphasis on making the implicit explicit. Every workflow is documented. Every architectural decision has a rationale. The system is opinionated because I am.
Professional framing
Every pattern in chris-os is designed to be transferable. The migration system works the same way whether the database has one user or a hundred. The privacy tier model maps directly to enterprise data classification. The multi-agent orchestration methodology scales from one person to a coordinated engineering team.
I'm looking for work where I can apply this stack: infrastructure architecture, AI integration, automation design, and the kind of full-stack thinking that connects a database schema to an edge worker to a voice interface. Consulting, fractional, contract.
The stack I work in
PostgreSQL
Schema design, role modeling, migrations, query optimization
Python
Data pipelines, ETL, scripting, ML tooling
TypeScript / Node.js
APIs, Fastify, React, Vite, Astro
Docker / Linux
Compose orchestration, networking, production ops
Cloudflare
Pages, Workers, R2, DNS, edge functions
AI / MCP
Claude, Ollama, multi-agent orchestration, custom proxies
n8n
Workflow automation, webhook routing, Pub/Sub integration
Home Assistant
IoT, voice, automation, custom integrations
Find me on GitHub . Or get in touch directly .