8+ years of experience building resilient systems with Go, Microservices, and Cloud Infrastructure. Currently focused on the intersection of scalable backend architecture and Production AI.
Recommendations
Building an AI Workflow That Can Reject Its Own Output
Most AI workflow demos follow a familiar pattern: connect a few model calls, pass the output of one into the next, and show the final result. The interesting engineering problems begin when one of those calls returns something that is valid JSON but wrong, or when a reviewer confidently approves an artifact it should have rejected. I ran into those problems while building FictionForge, a story-planning workflow I worked on as part of an applied AI engineering project....
When Bad Decisions Become Cheap to Execute
I can now generate an entire application faster than I could configure a local development environment a few years ago. With a few paragraphs of context, an autonomous agent will scaffold the directory structure, write database migrations, wire REST or gRPC endpoints, synthesize unit test suites, and generate Dockerfiles. The entire pipeline materializes in minutes. Yet being able to build things faster has not made anyone better at deciding what to build....
When Everything Becomes Easy, Nothing Feels Impressive
A few years ago, if an engineer told you they had designed, built, and deployed an entire full-stack application over a single weekend, you were genuinely impressed. Your immediate instinct was to interrogate the technical implementation. How did they model the schema? How did they manage session state and authentication? Which database engine did they choose, and how did they navigate its concurrency model? How did they stitch together routing, state synchronization, and deployment automation in 48 hours without collapsing under configuration fatigue?...
