Learning system / Engineering education
Senior SWE Pattern Trainer
A spaced-repetition system for training senior engineering judgment and situation recognition.
A learning product that teaches the invariant moves behind senior software engineering: what is moving, what can break, what must be true, and how to prove the system works.
Status
Live
Timeline
Built as a senior judgment training system
Domain
Engineering education
Why
Learning system
Stack
Languages, services, data sources, and operating pieces behind the build.
Code Proof
What The Build Actually Contains
LOC
3.9k+
Source files
23
Runtime
Cached
Loop
SRS
Product proof
Implementation
Code Behind The Surface
Training the invariant move
tsThe core move behind the product surface.
const review = gradeRecognition({
situation,
selectedMove,
expectedInvariant,
proofRequired,
});
scheduleNextRep(cardId, review.confidence);Product Model
tsThe useful answer has to be modeled before the UI can make it obvious.
type ProductSurface = {
input: "Engineering education";
signal: "Can senior engineering judgment be trained as pattern recognition instead of absorbe";
proof: string[];
};
const surface: ProductSurface = {
input: "Engineering education",
signal: "Lessons, drills, proof examples, and retrieval practice.",
proof: [
"Cached lesson curriculum",
"Spaced repetition cards",
"Track presets from fundamentals to distributed systems",
"Review history and card state"
],
};Hard Part
tsEvery build has a constraint: data quality, workflow shape, trust, speed, or operational risk.
const constraint = {
project: "Senior SWE Pattern Trainer",
status: "Live",
category: "Learning system",
hardPart: "The wedge is turning tacit judgment into a productized practice loop. It lowers the time needed to recognize p...",
};
shipSurface(constraint);Project Logic
Why This Exists
The point is not to show another screen. It is to show the gap, the build constraint, and the proof of work.
Mission
Can senior engineering judgment be trained as pattern recognition instead of absorbed only through painful experience?
Most engineering education teaches concepts in isolation. Senior engineers recognize situations: persistence risk, concurrency shape, deployment change, incident pressure, proof requirements, and what invariant move applies.
Build
What Had To Work
I built a study system with cached lessons, generated card banks, curriculum presets, review history, and per-card spaced repetition state.
Why It Matters
Situation -> invariant move
Turns senior engineering judgment into repeatable pattern recognition instead of waiting years for painful exposure.
Hard Parts
Make The Signal Useful
Package hard-won engineering judgment into a repeatable training loop with cached curriculum, deterministic study paths, and retrieval practice.
Turn The Work Into A System
I built a study system with cached lessons, generated card banks, curriculum presets, review history, and per-card spaced repetition state.
Prove The Wedge
The wedge is turning tacit judgment into a productized practice loop. It lowers the time needed to recognize patterns that usually take years of production exposure to internalize.
Decisions
Next Move
I would add team cohorts, scenario-based assessments, manager dashboards, and role-specific tracks for frontend, backend, infra, incident response, and AI product engineering.
Tell Me About Your Project
Bring Me The Bottleneck.
I’ll Build The Answer.
Tell me what people are trying to do, where the current path breaks, and what kind of useful answer should exist.
Market Gap
Demand exists, but the answer is missing.
Workflow Drag
The work is still too manual, slow, or scattered.
Product Wedge
A small surface could prove the larger opportunity.