I build systems that don't wake you up at 3 AM

What you get:

I'll review your architecture and tell you what's going to break before it costs you money. No sugar-coating. System design, technical strategy, and the kind of honest opinions that save you from expensive mistakes down the line.

My approach:

I've been woken up at 3 AM by production failures. My architectures are designed by someone who's paid the price for bad decisions. I optimize for three things: your AWS bill, your sleep schedule, and your sanity when you need to change something six months from now.

Good fit for:

• Companies where downtime costs actual money
• Teams stuck with legacy systems that need evolution, not rewrite
• CTOs who want a technical sounding board, not a yes-man
• Organizations where "move fast and break things" has lost its charm

What you get:

End-to-end systems built with functional programming principles. From frontend to backend to infrastructure, with proper testing, monitoring, and documentation. The kind of code you won't be embarrassed to maintain in year three.

Technology stack:

Frontend: React, Next.js, Astro, Alpine, Angular, SolidJS. Backend: F#, Scala (cats/zio), Rust, TypeScript with effect systems (Effect-TS, fp-ts). Cloud: Azure, AWS. Tooling: Monorepos (Turbo, Nx) for teams that actually need to coordinate. I choose technologies based on your constraints, not Twitter trends.

Good fit for:

• Systems that need to scale without turning into a maintenance nightmare
• Teams who care about type safety and don't want to debug undefined at 2 AM
• Projects where functional programming actually makes sense (not everything needs monads)
• Organizations tired of "it works on my machine"

What you get:

RAG systems that actually work, LLM integrations that don't bankrupt you, and AI strategy that's grounded in reality. I'll help you figure out what AI can actually do for your business versus what the hype cycle promises.

My approach:

AI is a tool, not magic. If someone promises you AGI in your CRM, run. I focus on boring, proven patterns: embedding pipelines that work, retrieval that's fast enough, prompts that don't hallucinate your business into legal trouble. Cost-effective solutions with realistic ROI expectations.

Good fit for:

• Companies tired of AI demos that never make it to production
• Organizations that need RAG systems with actual retrieval quality
• Teams who want to understand their LLM costs before the bill arrives
• Businesses exploring AI without drinking the Kool-Aid

What you get:

Software architecture for legal systems, compliance platforms, contract management, and legal document processing. I understand both the technical architecture and the legal requirements — completed my LLB in 2025, because apparently 18 years of software wasn't enough.

My approach:

Most developers don't understand legal requirements. Most lawyers don't understand software architecture. I speak both languages. I've designed systems that process health data, financial transactions, and legal documents — domains where mistakes aren't just expensive, they're liability.

Good fit for:

• Law firms modernizing their practice management systems
• Companies building compliance or contract management platforms
• Organizations that need someone who understands both code and law
• LegalTech startups tired of explaining legal concepts to developers

What you get:

Honest architecture audits that tell you what's actually going to fail. I'll review your code, infrastructure, and decisions, then deliver a report with the things that will cost you money if you ignore them. Prioritized by "fix this now" vs "fix this before your Series B."

Deliverable:

A detailed report you can actually act on: findings ranked by risk and cost, recommendations that consider your constraints, and an implementation roadmap that doesn't assume unlimited budget. No consultant speak, just what needs to happen.

Good fit for:

• Due diligence before acquisition (someone needs to read that code)
• Pre-funding tech assessment (VCs will ask someone, might as well be someone honest)
• Production systems that make you nervous
• Second opinions when your gut says something's wrong