Full-stack web applications
End-to-end typed systems with Next.js App Router, server components, and PostgreSQL. Built to handle real load, not just demo traffic.
I build systems, break them, and document everything.
This portfolio exposes a public REST API. Request a key →
End-to-end typed systems with Next.js App Router, server components, and PostgreSQL. Built to handle real load, not just demo traffic.
Schema design that survives the second year, not just the first sprint. Prisma migrations, query optimization, and data integrity as a first-class concern.
REST APIs with OpenAPI specs, rate limiting, and versioning. The kind of DX you'd want if you were the consumer.
Every project ships with a postmortem. Every decision gets written down. The next engineer reads the docs, not the chat history.
The portfolio itself demonstrates these principles. Explore the public API →
It started with curiosity. Before frameworks, before stacks, before architecture — there was just a problem I wanted to solve. That first line of code that actually ran changed everything. I didn't know what I was building, but I knew I couldn't stop.
Curiosity became obsession.
I started building anything and everything. Some projects worked. Many didn't. I broke more things than I fixed, and I documented every failure along the way. The mistakes weren't setbacks — they were the actual curriculum. That's where the real education happened.
Failures became features.
I stopped thinking in features and started thinking in systems. How does data flow? What breaks under pressure? How do you build something that scales — not just technically, but mentally? My background in trading sharpened this lens. Every system has signals. Every failure has a pattern. I build with that in mind.
Ship. Break. Learn. Repeat.
"Brian has a rare ability to take a vague problem, break it down into something concrete, and ship a solution that actually holds up under pressure. Worked alongside him on a logistics API and his attention to edge cases saved us from a very bad production incident."
"He doesn't just build what you ask for — he asks why you need it. That instinct to question assumptions before writing code made every sprint more productive. One of the most thoughtful engineers I've collaborated with."
"Brian led our engineering team through a tight deadline with zero drama. He set a clear technical direction, delegated well, and was the first person to raise his hand when something went wrong. That kind of ownership is hard to find."
"I reached out to Brian for mentorship when I was stuck on my first real project. He didn't give me the answer — he walked me through the thinking. Three months later I had my first job offer. I'm convinced that conversation made the difference."
"Solid backend developer with a good grasp of infrastructure. He understood the deployment constraints from day one and built the API in a way that made our Docker setup significantly simpler. Clear communicator, reliable on deadlines."
"Brian joined as an intern and within two months was contributing to architecture discussions. His documentation habit is exceptional — every PR comes with context, every decision has a reason. He made the whole team better by raising the bar on how we write things down."
One VPS runs the portfolio you're reading, its admin CMS and public API, and a self-hosted relay that fans one OBS stream out to YouTube and Facebook — two apps, two databases, one firewall.
I work with early-career engineers who want honest feedback, not cheerleading. Limited spots open.
Architecture, patterns, and honest feedback on your real projects.
Job search strategy, interview prep, and early-career decisions.
Async or live sessions built around where you are and where you want to go.
Name one tradeoff per claim. Credibility comes from disclosure, not from sounding sure.