Long-form writing on software engineering, systems design, and building things. (Page 3)
The app/services directory starts with good intentions but often decays into a junk drawer. We'll diagnose the symptoms of a service directory in crisis and explore how patterns like Form Objects, Commands, and Query Objects can restore clarity and maintainability to your Rails app.
Move beyond hardcoded strings and build a scalable, version-controlled, and testable prompt management system in Rails to manage your AI prompts like professional software.
A hardcoded prompt typo cost us $2,400 in 72 hours. Here's the engineering discipline, testing strategies, and open-source tool (Promptly) we built to fix it for good.
Your async AI feature works... until it doesn't. This guide covers how to debug unreported job failures, trace Action Cable WebSocket issues, and handle common pitfalls in production.
A deep dive into architectural patterns using ActiveJob and Redis to solve LLM latency, moving from an 8-second wait to a sub-50ms cached response.
Most function calling tutorials show toy examples that break in production. This guide provides the 80% foundation you actually need: a security-hardened, multi-turn agent with complete parameter validation, proper error handling, logging, and timeouts. Copy, customize, and build on it
An advanced guide to building a robust, automated RAG evaluation framework in Rails, with production-minded code for metrics, parallelization, and CI/CD integration.
A user double-clicks "Pay Now." Are they charged twice? In a world of unreliable networks and automatic client retries, idempotency isn't an advanced feature—it's a fundamental requirement for any robust API. This post shows you how to implement it using the Idempotency-Key header pattern in Rails.
A Pull Request is more than a gate; it's a story. It's the most critical piece of documentation your team will ever write about a change. This post breaks down the anatomy of a great PR, transforming it from a chore into a powerful tool for communication, collaboration, and future debugging.
Most teams see feature flags as simple on/off switches. They are so much more. This post explores how to use flags for percentage-based rollouts, targeted betas, and even as operational circuit breakers, transforming them from a developer convenience into a strategic tool for shipping safer, better software.