COHORT-04 Spring intake closes Friday · 84 seats left of 120

Learn one thing
this week.
Actually learn it.

Field Guide ships focused, four-week courses on the systems you skim over but should understand. Twelve lessons. Real exercises. Office hours with people who built the thing.

12 cohorts running concurrently
· 62% completion rate (industry: 8%)
fieldguide.dev/postgres-for-app-engineers
FG-014 · DATABASES
Postgres for application engineers
4 weeks · 12 lessons · ~3.4 hrs / week
In progress
3 of 12
Week 1 · Indexes that matter
L01 · How a B-tree actually reads 18m
L02 · When to add an index (and when not) 22m
L03 · Partial & expression indexes 26m
L04 · Reading EXPLAIN ANALYZE
Next up · est. 28 min · 1 exercise
Resume →
L05 · Composite indexes & sort order 31m
L06 · Week 1 capstone · exercise 45m
Week 2 · MVCC & locking
L07 · Why two readers see two truths 24m
L08 · FOR UPDATE vs. advisory locks 26m
118 engineers reading this lesson now
Engineers learning here from 408 companies
Linnea forecast Glide Vantage Mercury Brightwave Nimbus Coast Halcyon quartermast Northwind Foundry & Co Linnea forecast Glide Vantage Mercury Brightwave Nimbus Coast Halcyon quartermast Northwind Foundry & Co
28,408
Active learners this month
62%
Course completion rate
industry avg: 8%
47
Deeply-curated paths
12
Cohorts running this quarter
— Why this works

Three habits we steal from good teachers.

01 · Structured paths

Twelve lessons, not twelve hundred.

Every Field Guide is exactly four weeks long. The lessons add up. By Friday of week three you can do something on Monday of week one you couldn't have explained in a code review.

  • ~3.4 hours per week, paced not video-padded
  • Each lesson ends with a 5-minute receipt
  • Weekly capstone exercises, hand-graded
FG-014 · 4 weeks syllabus
Week 1
Indexes that matter
Week 2
MVCC & locking
Week 3
Vacuum & bloat
Week 4
Replication, in anger
Capstone: diagnose a real slow query from a fixture DB. 30 min, hand-graded.
Exercise · 04.2 passed · 3/3
Add the index that makes this query run in < 5ms.
Fixture: orders · 1.4M rows · customer_id, status, created_at
-- before · 1.18s
SELECT id, total
FROM   orders
WHERE  customer_id = 38402
  AND  status = 'paid'
ORDER BY created_at DESC
LIMIT  20;
your answer
CREATE INDEX orders_cust_status_created
  ON orders (customer_id, status, created_at DESC);
Before
1.18s
P95 · seq scan
After
4.2ms
P95 · index scan
Speedup
281×
−99.6%
02 · Exercises that grade themselves

Type a query. See your plan. Get a verdict.

Every Field Guide ships with fixture databases and a sandboxed runner. Type your SQL, see EXPLAIN ANALYZE rendered, find out whether you actually moved the needle.

  • Real fixture data, not toy schemas
  • Per-exercise pass criteria, not "did it run"
  • Hand-graded capstones with written feedback
03 · Cohorts (optional)

Take it with twenty people who care.

Opt into a four-week cohort and you get a live office-hour every Thursday, a private Discord with the instructor, and a shared weekly capstone review. Or stay solo — same lessons, your timetable.

  • Office hours: Thursdays, 60 min, recorded
  • ~20 learners per cohort, capped on purpose
  • Printed certificate on completion (a real PDF, optional)
Cohort · Spring 26 Thu · 6PM CET
Office hours · Week 2 · MVCC
with Marcus Tobin · Founding Engineer at Forecast
+11
Priya shared a question 2m
Hana turned in W2 capstone 14m
Marcus posted Friday Q&A recap 1d
— Code blocks

Annotations in the margin. Like a textbook should have.

Every code block in a Field Guide lesson can have side notes that point at specific lines. Hover a margin note, the line lights up. Read once, learn once.

L04 · Reading EXPLAIN ANALYZE · 28 min read
1
2
3
4
5
6
7
8
9
10
11
12
13
-- before: 1.18s on 1.4M rows
EXPLAIN ANALYZE
SELECT id, total
FROM   orders
WHERE  customer_id = 38402
  AND  status = 'paid'
ORDER BY created_at DESC
LIMIT  20;

Seq Scan on orders  (cost=0..38402.18 rows=18)
  Filter: (customer_id = 38402 AND status = 'paid')
  Rows Removed by Filter: 1,408,118
Planning Time: 0.18 ms · Execution Time: 1184.42 ms
Marked up by Marcus Tobin · Founding Engineer at Forecast L04 of 12 · "Reading EXPLAIN ANALYZE"
— ⌘K search

Find the lesson, not the playlist.

Type what you actually need to learn. Field Guide returns lessons, exercises, and the specific minute marks in office-hour recordings where it was discussed.

how do I read EXPLAIN|
esc
Lessons · 3 results
L04
Reading EXPLAIN ANALYZE
Postgres for application engineers · 28 min
L09
Buffer cache and how to read EXPLAIN BUFFERS
Postgres internals · 38 min
L02
When to add an index (and when not)
Postgres for application engineers · 22 min
Office hour recordings · 2 results
Q: "what is 'cost' supposed to mean in EXPLAIN?"
Cohort 03 · Marcus Tobin · jump to 18:42
Walk-through of a real bad EXPLAIN from Linnea prod
Cohort 02 · Priya Anand · jump to 31:08
↑↓ navigate open . filter type 38ms · across 47 courses
— Currently in the catalog

47 guides. All four weeks. All deep.

FG-014 · Databases popular
Postgres for application engineers

Indexes, MVCC, vacuum, replication — the four things you wish your senior had explained.

4 weeks · 12 lessons·Marcus Tobin
3 / 12
FG-009 · Systems new
Distributed systems in 4 weeks

Consensus, replication, CAP without the buzzwords. By the end you can read a paper and explain it.

4 weeks · 12 lessons·Ines Calderón
Next cohort May 06
FG-021 · Languages solo only
Rust ownership, in anger

Borrow checker, lifetimes, async. We build a small server and break it on purpose, six times.

4 weeks · 12 lessons·Yusuf Abara
Solo · self-paced
FG-031 · Theory
Type theory for working engineers

From "what is a sum type" to ADTs, GADTs, and HKTs — with TypeScript snippets, not papers.

4 weeks · 12 lessons·Hana Suzuki
Next cohort June 03
FG-008 · Frontend
React performance, measured

Profiler, suspense, server components — and how to tell which of them you actually need.

4 weeks · 12 lessons·Priya Anand
Self-paced
FG-018 · Networking last 14 seats
TCP, TLS, and HTTP/3 in 28 days

What's actually on the wire when you open google.com — handshake, multiplexing, QUIC, ALPN.

4 weeks · 12 lessons·Marcus Tobin
Next cohort starts Apr 22
— Pricing

Buy a guide. Or all of them.

Every plan includes lifetime access to lesson material, the sandbox runner, and the alumni Discord. Refunds within 14 days, no form.

Single course one-time
$99 / guide

Pick one, own it forever. Solo by default — cohort access is +$49.

Browse the catalog →
  • Lifetime access to one guide
  • All 12 lessons, exercises, capstones
  • Sandbox runner with fixtures
  • Printable completion PDF
  • ·Cohort access sold separately ($49)
Most popular
Subscription all 47 courses
$24 / month · billed monthly

Everything in the catalog, plus every new guide we ship.

Start the 14-day trial →
  • All 47 guides, future included
  • Solo mode unlimited
  • 2 cohort enrollments per quarter
  • Office-hour recordings library
  • $49 cohort upgrades
  • Refunds: 14 days, no form
Team 5+ seats
$14 / seat / month

For engineering managers who want learning to show up in their reports.

Book a 20-min call →
  • Per-seat pricing from 5 to 200
  • Manager dashboard with progress
  • Private team cohorts available
  • Curated learning paths by role
  • SSO + invoicing + DPA
— What learners say

From the people who actually finished.

Postgres for app engineers

I'd been "doing SQL" for nine years and reading EXPLAIN was still a vibe check. After Week 1 I rewrote a query at work, 1.18s → 4.2ms. Paid for the cohort in one afternoon.

Priya Anand
Staff Engineer · Linnea · Cohort 03
Distributed systems · 4 weeks

The pacing is the whole magic. I bounced off Designing Data-Intensive Applications twice. Four weeks of 3.4 hours got me further than four months of "I'll read it on the weekend".

Hana Suzuki
ML Lead · Glide · Cohort 02
Team plan · Brightwave

We put six engineers through the Postgres guide as a team cohort. The shared capstone became our weekly internal lunch-and-learn. Three months later, our P95 query latency is down 42%.

Ines Calderón
Head of Eng · Brightwave

Common questions, straight answers.

How is this different from Egghead or Frontend Masters? +
Both are great catalogs of standalone videos — Field Guide is the opposite. We ship four-week, twelve-lesson structures with paced exercises, weekly capstones, and a hand-graded review. You're meant to finish, not browse. Our completion rate is 62%; most platforms quote around 8%.
Are courses video-heavy or text-heavy? +
Text-first. Most lessons are written, with embedded diagrams, runnable code, and a short (2–4 minute) video where the instructor walks through the trickiest bit. You can finish a lesson without unmuting. Office hours are video-only — those are recorded and transcribed.
Can I get a refund if I bounce off a course? +
Yes — 14 days from purchase, no form, no questions. Click the refund button on the order page, the charge reverses. For team plans we'll pro-rate. Around 4% of orders refund; we'd rather it be easy than have an unhappy alum tweeting.
How long do I have access after purchase? +
Forever, on the single-course tier — lesson material, exercises, sandbox runner, alumni Discord. On Subscription, access is for the duration of your plan. Cohort recordings stay with you regardless of subscription, attached to your account.
Do you offer team licenses for engineering managers? +
Yes — $14/seat/month from 5 seats up to 200. Includes a manager dashboard with per-engineer progress (private to the manager, opt-in transparency to the team), curated learning paths by role, and the option to run a private team cohort. Custom onboarding and invoice billing on request.

One week. One thing. Actually learn it.

Try Lesson 01 of any guide for free — no email required.