If a company has successfully made the shift into tools like Claude Code then the number of concurrent tasks individual developers are managing has gone up. It’s not because they're writing more code (in many cases we're writing less), it’s because the bottleneck has moved. What does the future state look like and how can be tool this in the intermediate?

Large architectural decisions (service boundaries, messaging strategies, consistency models) are important. But they are not where most systems fail. How can we build quality gates to catch coupling & cohesion regressions?

Every company should run an analysis to classify pull requests and to trace bugs to their root causes. This was previously impossible and no DORA tool will do it for you. The insights are tremendous.

How to integrate dataloader with @nestjs/graphql in a federated GraphQL architecture. This guide covers resolver patterns, request-scoped loaders, and efficient reference resolution to eliminate N+1 queries.

A deep dive into best practices for scaling Node.js applications in Kubernetes, focusing on CPU-based autoscaling, API latency budgets, and architectural patterns that keep systems predictable and resilient.

A framework for writing effective engineering documents by aligning with reader intent. Tailor standards, design docs, and tech evaluations for clarity, impact, and better decision-making.

BFFs once promised better developer experience and tailored APIs—but over time, they introduced complexity, duplication, and architectural drag. In this post, I share why we’re retiring our BFF layer in favor of a leaner, more maintainable “2.5-tier” approach—and what others can learn from our evolution.