2026

  1. Sprints Are the Wrong Unit for AI Delivery

    MCP and LLM tooling make delivery, reporting, and testing more continuous. That changes what teams should optimize for.

    ai / llms / software delivery
  2. Indexes are not free

    Adding an index speeds up reads. It also slows down writes, increases storage, and adds a maintenance burden that compounds over time.

    postgres / database / architecture / software engineering
  3. The Cost of Making Everything Real Time

    Real time sounds like an obvious improvement until you price it. The useful question is not how fast the data can arrive, it is how often anyone actually acts on it.

    data / architecture / product engineering / software engineering
  4. Why RAG Fails in Production

    Most RAG systems fail at retrieval, not generation. The fix is usually better evidence, ranking, and product logic.

    ai / llms / architecture / software engineering
  5. What Zero-Downtime Deployment Actually Requires

    Zero-downtime deployment depends on overlapping versions, safe traffic shifts, and database changes that work before and after release.

    devops / architecture / database / software engineering
  6. Evals Are Not Tests

    Unit tests tell you when code breaks. Evals tell you if your LLM is still answering the right question. These are different problems, and treating them the same way is how AI products degrade silently.

    ai / llms / software engineering / braintrust
  7. Idempotency Is Not a Nice-to-Have

    Every retry, webhook, and payment system depends on idempotency. Most engineers treat it as an afterthought. Here is what happens when they do, and what it actually takes to build operations that are safe to repeat.

    architecture / distributed systems / software engineering
  8. Event-Driven Architecture Without Kafka

    Most teams reach for Kafka too early. Here is how to build a production event bus with Celery and Redis, the patterns that make it reliable, and the four conditions where Kafka actually earns its place.

    architecture / kafka / software engineering / redis
  9. Per-PR preview environments on Docker Swarm

    How to give every pull request its own live URL using Docker Swarm, Traefik, and a wildcard DNS record, without running a Kubernetes cluster.

    docker / devops / github-actions
  10. What a Data Pipeline Actually Is

    ETL has three letters. Most people can explain two of them. The third is where teams make decisions that shape who owns data, when it is trustworthy, and how hard it is to change.

    data / architecture / engineering / software engineering
  11. The Difference Between a Queue and a Stream

    Queues move work forward. Streams preserve a history consumers can read from. That difference changes ownership, replay, and failure handling.

    architecture / kafka / redis / software engineering
  12. AI Tools Are Not Magic Bullets

    LLMs are not magic bullets. They are powerful translation engines for messy data, especially when you use them to summarize, structure, and move information between systems.

    ai / llms / data / software engineering
  13. Context Engineering Is Not Prompt Tuning

    Prompt engineering focuses on the question. Context engineering focuses on the world you hand the model before the question. That distinction changes how you design reliable LLM systems.

    ai / llms / software engineering / platform engineering
  14. AI Scalability: What It Actually Means for Software Architecture

    AI can generate working software quickly, but AI scalability depends on architecture, constraints, and disciplined engineering after the proof of concept.

    architecture / scalability / ai / software engineering
  15. Safe Database Migrations at Scale

    A migration that passes in staging can lock a busy production table for minutes. The difference is not the migration. It is the assumptions behind it.

    postgres / database / architecture / software engineering
  16. Why Search Is Such a Hard Thing to Talk About

    Search sounds like one feature, but it is really a bundle of product decisions, customer expectations, matching strategies, ranking tradeoffs, and business context.

    search / postgres / product engineering / software engineering
  17. Observability Is Not Logging

    Adding more logs does not make a system observable. Observability is the ability to ask questions about a running system that nobody anticipated when the system was built.

    observability / platform engineering / software engineering

Areas of expertise

Browse by topic

Start with a subject, then follow the related articles through the decisions behind it.