Ruchit Suthar · Software architect & technical leader

AI writes the code.
You still make the call.

Fifteen years of architecture calls, hiring decisions, and technical debt I had to pay down myself. I write down which ones held up and what the rest cost. I'm still on call for the ones I get wrong.

Start ReadingWhat's on the site
128Articles10Pathways6Reference3Tools

Featured

Start here

Four ways in, depending on what you came for.

Everything on the site is one of these four. If you are not sure which you need, start with the writing.

ReadWritingArguments and post-mortems from production. Come here for the reasoning behind a decision, including the ones I got wrong.128articlesLearnPathwaysOrdered sequences where each chapter assumes the one before it. Your place saves as you read, so a pathway survives being put down for a week.10pathwaysLook upReferenceCatalogs, matrices and latency tables, each stamped with the date it was last re-checked. Numbers you can put in a deck without hedging.6reference docsComputeToolsError budgets, capacity envelopes and decision records, worked out in the browser against your own numbers.3tools

There is also a glossary of 63 terms for the vocabulary the rest of the site assumes you share.

Top picks

If you read six things here, read these.

Not the newest. These are the six I hand to people who ask where to start, with the reason each one earns the slot.

All writing →
  1. Start hereThe Codebase Only AI Understands: Why 3am-Fixability Is the Metric Nobody's TrackingThe test I apply before AI-written code ships: could you fix it at 3am with nobody to ask. Everything else I believe about architecture falls out of that one question.Software Architecture13 min read
  2. Asked for mostTechnical Debt: When to Pay It Down, When to Ignore It, and How to Explain the Trade-OffsTeams lose the debt argument because they bring feelings to a budget conversation. This is the version that holds up in a room with a CFO in it.Software Architecture12 min read
  3. If you just took the jobYour First 90 Days as CTO: A Practical Playbook for Startup and Scaleup LeadersWhat to actually do in the first three months, in order, before the organisation decides who you are and stops listening.Technical Leadership18 min read
  4. Before your next metrics deckMeasuring Developer Productivity: DORA, SPACE, and What Actually WorksDORA and SPACE get quoted by people who have never run them. Here is what each one can and cannot tell you about your team.Developer Productivity14 min read
  5. The uncomfortable oneDoes AI Kill Craft? Taste, Judgment, and Quality in the Age of Generated CodeGenerated code raised the floor and did nothing for the ceiling. What is left that only judgment can do — and how you keep it.Quality & Craft12 min read
  6. The one I stand byLeading by Leaving: Why I Don't Answer Work Messages After 7 PMI do not answer work messages after 7pm, and the team got better rather than worse. The mechanism, not the platitude.Career & Life Design14 min read

The workbench

Run the numbers before you argue about them.

Everything runs in the browser. No sign-up, and your inputs never leave your machine.

All tools →
tool.01SLO & Error Budget CalculatorTurn an availability target into allowed downtime, a request budget, and a burn rate you can actually alert on.Open tooltool.02Capacity CalculatorDAU to peak QPS, bandwidth, storage and instance count — with the multipliers that decide whether the estimate is any good.Open tooltool.03ADR GeneratorFill in the decision, get a clean Nygard, MADR 4.0 or Y-statement architecture decision record — copied or downloaded as markdown.Open tool

Subjects

Six things I write about.

Each one keeps its own archive. The pick under each is where I would start you if the subject is new.

Every article →
39articlesSoftware ArchitectureSoftware architecture for systems that outgrew their original design. Trade-offs, failure modes, and the calls that only looked obvious afterwards.Start withI Over-Engineered a SaaS for Millions. It Got 3 Users.
31articlesTechnical LeadershipTechnical leadership after the promotion: hiring, honest feedback, and team structure. Drawn from 1,000+ interviews and 25+ engineers led.Start withThe Conversation-Based Interview: How I Evaluate 7-8 Year Experienced Engineers
24articlesDeveloper ProductivityDeveloper productivity now that the bottleneck is judgment, not typing speed. AI workflows, deep work, and metrics that survive a review.Start withAI-Driven Development: The Spec-First Workflow That Makes Agents Actually Useful
18articlesCareer & Life DesignEngineering career decisions made with the care you would give an architecture decision. The IC-to-leadership fork, boundaries, and pacing.Start withEnergy Management for Engineers: Your Calendar Isn't the Real Bottleneck
11articlesQuality & CraftSoftware craftsmanship borrowed from watchmaking and long-horizon design. Why quality compounds, and why the shortcut always sends an invoice.Start withThe Craft of Software: A Philosophy of Quality That Ships
5articlesFounder Tech DecisionsThe technical calls you cannot undo: scoping, hiring, cost and risk. Written for the founder signing the cheque rather than the engineer doing the build.Start withHow to Interview a Developer When You Can't Judge Code

Pathways

When you want the whole argument, in order.

10 sequences that build chapter on chapter, with your place kept as you read. Start at the top or jump to the chapter you need.

All pathways →
Agent EngineeringMost of it is distributed-systems discipline you already have. One cost is new — and nobody's pricing it.7 chapters1h 30minIntermediate to Advanced
System Design MasteryFrom first principles to production-grade architecture.8 chapters1h 49minBeginner to Advanced
The Pragmatic Tech LeadFrom senior engineer to engineering leader without losing your soul.7 chapters1h 26minIntermediate to Advanced
AI-Augmented DeveloperUse AI tools to multiply your output without losing craftsmanship.6 chapters1h 9minBeginner to Intermediate
Becoming a Software ArchitectWhat it actually takes to become — and operate as — a software architect. The ladder, the day-to-day, the deliberate practice.6 chapters1h 6minSenior Engineer to Architect
Career ArchitectureDesign the engineering career you actually want — not the one that happens to you.5 chapters58minIntermediate to Advanced
Scaling Systems & TeamsNavigate the inflection points where engineering organizations break — and learn to build through them.6 chapters1h 12minIntermediate to Advanced
Engineering Excellence at ScaleMove fast without breaking things — by building the practices that make quality the default.6 chapters1h 10minIntermediate to Advanced
Engineering Leadership in the AI EraLead engineers, ship quality, and adopt AI without losing the plot.5 chapters25 minIntermediate to Advanced

About

Who writes this.

Ruchit Suthar

Ruchit Suthar

Software architect & technical leader

The long version

Fifteen years in, the question I ask about my own work has changed three times: first how much I could ship, then how well it held up, and now whether it was the right thing to build at all. Output, then quality, then judgment.

Everything here comes out of that third question. Systems in production, teams that had to be hired and kept, and decisions that only looked obvious afterwards.

15+

Years in production

1,000+

Technical interviews

25+

Engineers led

Working together

128 articles · 10 pathways · 6 reference docs

Architecture, leadership, and craft, written for engineers who make the call.

Every article here is anchored to a system I shipped or a call I got wrong. Nothing on this site could run on another engineer's blog without changing a word.

Browse the archiveExplore Pathways
The right architecture is the one your on-call can fix at 3am without you. Every clean-on-paper decision I have regretted looked fine in the design review and cost someone else their night. Recoverability beats elegance every time it actually matters.
Ruchit Suthar