Section300
Projects
Six systems, written up the way I would review them: what was at stake, what constrained us, which options we rejected, and what shipped. Each follows the same order: problem, constraints, architecture, decisions, outcome, lessons.
- 301From one data center to three continentsTaking a founder-built platform from a single data center to cloud regions in North America, Europe and Asia, with traffic routed by geography.
- 302Making a publishing platform compete on distributionSetting technical strategy for a portfolio of media titles, and treating search and social reach as platform capabilities.
- 303Modernizing a public-sector service without a big-bang rewriteReplacing a legacy public-facing service incrementally, using a strangler pattern, Django and React on AWS, and infrastructure as code.
- 304LLM document processing with a human in the loopDesigning an LLM pipeline that extracts and classifies documents, grounds answers in the client’s own policy through retrieval, and sends low-confidence results to a person.
- 305Event-driven microservices that stay consistentMoving a platform from tightly coupled synchronous calls to Kafka-based events, using a transactional outbox and idempotent consumers.
- 306Capacity planning across 2,000+ collocationsIntegration, expansion and capacity planning for ATM, IP, VoIP and OC infrastructure across a national broadband footprint.