What I've Built
Projects that taught me things
Maersk logistics (solo)
Months out of bootcamp, I was handling enterprise logistics for Maersk as a solo developer. Complex API integrations, German customs systems, XML parsing, airline industry algorithms. Data for 15 distinct offices. Work that should require a team of 5-10 people.
The numbers that stuck with me: cleaned up a database from 13.3 million records down to 406,000. Analyzed an import integration process spanning 1200+ lines of code. Proposed infrastructure consolidation that would save €90/month.
Did on-site user research with five stakeholder roles. Found that one workflow forced 23 manual updates when users couldn't exclude items from bulk actions on 25 shipments.
Panopticron
Monitoring system for a 6-person agency. Real-time data sync from Vercel and GitHub, self-monitoring capabilities. Refine + Next.js + Supabase. It works. People use it.
Uroboro
Knowledge work insights were getting lost. Built a tool for 10-second capture, local AI processing, zero cloud dependency. Started at 17 commands and 1558 lines of code, refined down to 3 essential CLI commands.
Examinator
Needed to learn security concepts. ADHD-friendly, offline-first study tool. 186 flashcards, 7 summary documents, local LLM for generating practice questions.
The pattern
I hit a problem. I document what's actually wrong. I build something to fix it. If it works, I keep using it. If it helps others, even better.
The spite helps. When institutional knowledge gets punished or lost, documenting it becomes both survival strategy and motivation.