Compile
The room wheresenior engineersfinally learn slowly.
A quiet monthly membership for mid-career backend and full-stack engineers. Deep architecture content, peer code reviews, and async mentorship threads that compound — not content that just fills a feed.
The weekly rhythm
A place with familiar corners.
Not a content feed. Not a Discord server where every question gets an emoji and no answer. A schedule you can depend on — the same four corners, every week.
Tuesday · 11 AM ET
Office Hours
Bring the architecture decision you've been avoiding. A staff engineer walks through it live — no slides, no prep, just thinking out loud on a shared doc.
Thursday · Async drop
Architecture Teardown
One real system dissected: the database schema that didn't scale, the event bus that made it worse, and the rewrite that took 14 months. No happy endings edited out.
Open always · Async
Code Review Threads
Submit a PR that's been sitting in draft. Members comment. You respond. The thread stays open until you actually understand the feedback — not just merged and forgotten.
Monthly · Last Friday
Promotion Packet Review
One member shares their staff-level promotion case. The group reads it. We rewrite the parts that undersell the architecture decisions and cut the parts that sound like a resume.
"I spent two years watching conference talks on 2x speed. One Thursday teardown taught me more about distributed systems than any of them."
— Priya Mehta, Staff Engineer at Razorpay
The neighbors
People who closed the thirty-seven tabs.
Real members. The number crossed out is their Slack unread count when they joined.
Kwame Asante
Senior Backend Engineer · Stripe
Since joining: Rewrote our payment retry logic from scratch after the Thursday teardown on idempotency. Zero duplicate charges in 4 months.
Ananya Krishnamurthy
Full-Stack Engineer → Staff · Razorpay
Since joining: Used the promotion packet review to reframe my impact narrative. Got the staff title six weeks later.
Marcus Webb
Backend Engineer · Shopify
Since joining: Shipped a proper event-sourcing pattern for our inventory service. First PR in two years that didn't get a "let's talk about this" comment.
Layla Hassan
Senior Engineer · Cloudflare
Since joining: Submitted a draft RFC for our edge caching layer to the async review thread. Got back 12 comments that each took me a day to understand. Worth every one.
Tomás Reyes
Full-Stack Engineer · Linear
Since joining: Finally understand CQRS. Not the blog post version — the actual tradeoffs version.
The curriculum
Organized by where you are,
not by topic.
Choose your level. Read the table of contents. Then unlock one full lesson free — no credit card.
Database Foundations That Don't Lie
Indexes, query plans, and the three questions you should ask before adding any column.
- Reading a query execution plan without guessing
- When to normalize and when to stop
- Migrations that don't lock your table at 2 AM
- The N+1 problem: why it survives code review
API Design as a Contract
REST, versioning, and error handling from the perspective of the engineer who has to maintain it in year three.
- Versioning strategies that don't punish your consumers
- Error responses worth reading
- Idempotency keys: the 20-line change that prevents duplicate payments
Testing What Actually Breaks
Unit tests are table stakes. This module is about the tests that catch the failures that matter.
- Contract testing between services
- Property-based testing for edge cases you didn't think of
- Load testing before the load finds you
Distributed Systems Without the PhD
The CAP theorem, eventual consistency, and how to explain the tradeoffs to a product manager in one sentence.
- Consistency models you'll actually encounter
- Designing for failure: timeouts, retries, circuit breakers
- Event sourcing: the honest version (including what it costs you)
- Saga pattern for distributed transactions
System Design for Real Constraints
Not the interview version. The version where you have a legacy codebase, three engineers, and a hard deadline.
- Strangler fig pattern in practice
- Incremental migration without a big-bang rewrite
- Capacity planning with actual numbers
Writing That Gets Architecture Approved
RFCs, ADRs, and how to write a technical proposal that survives a skeptical principal engineer.
- Anatomy of an RFC that gets merged
- Documenting the decision, not just the decision
- Getting buy-in from people who weren't in the room
Technical Strategy Across Teams
How to influence architecture decisions you don't own and won't be blamed for.
- Platform thinking: building for builders
- Technical debt as a business conversation
- Engineering principles that survive turnover
The Promotion Packet That Actually Works
Based on 40+ real packets reviewed in Compile. What the good ones have in common.
- Framing impact at the right altitude
- The scope mistake that kills most senior→staff packets
- Evidence vs. assertion: what reviewers actually read
Free this week
Idempotency Keys: The 20-Line Change That Prevents Duplicate Payments
Senior-Ready · Module 1
Membership
One room. One price.
No tiers. No annual gotcha. Cancel any month. The seat stays yours as long as the membership does.
Less than one conference ticket. More useful than twelve.
- All architecture teardowns (Thursdays, async)
- Weekly office hours with a staff engineer (Tuesdays, live)
- Async code review threads — open until you understand
- Monthly promotion packet reviews
- Full curriculum: Senior-Ready → Principal Prep
- Member-only Slack (quiet, no noise policy enforced)
- Searchable archive of every teardown since launch
"The best $49 I spend each month is the one that makes the other $4,000 of conference tickets feel unnecessary."
— Kwame Asante, Senior Backend Engineer, Stripe