Progress Tracker
Auto-updated after each quiz. Latest at the top.
Summary
| Metric |
Value |
| Days completed |
10 |
| Current streak |
10 |
| Diagnostic score |
7.1 / 10 (71%) |
| Day 1 score |
7.5 / 9 (83%) |
| Day 2 score |
7.5 / 9 (83%) |
| Day 3 score |
8.15 / 9 (90.6%) |
| Day 4 score |
5.95 / 9 (66%) |
| Day 5 score |
7.55 / 9 (84%) |
| Day 6 score |
8.65 / 9 (96.1%) 🎉 |
| Day 7 score |
8.7 / 9 (96.7%) 🎉 |
| Day 8 score |
9.0 / 9 (100%) 🎯 |
| Day 9 score |
9.0 / 9 (100%) 🎯🎯 |
| Day 10 score |
9.0 / 9 (100%) 🎯🎯🎯 THREE-PEAT |
| Average |
~89% (climbing) |
| Trend |
📈 5 consecutive 96%+ quizzes, 3 consecutive perfects |
| Assessed level |
Staff — genuine Postgres storage-engine depth (visibility map, HOT updates, partial-predicate immutability, sargability) |
| Next up |
Day 11 — Replication (leader-follower, multi-leader, leaderless) |
Phase status
- Phase 1 (Foundations, Days 1-7): ✅ COMPLETE
- Phase 2 (Data & Storage, Days 8-14): In progress — Days 8, 9, 10 ✅ done, Day 11 next
Chronic gaps
All resolved. No gap has failed on 2+ consecutive tests since Day 8.
| Gap |
Status |
| Tail-amp |
✅ Resolved & maintained |
| Bandwidth vs latency |
✅ Resolved |
| JWT vs sessions |
✅ Resolved |
| Push-mechanism directionality |
✅ Resolved |
| Capacity math in architecture answers |
✅ Resolved |
| DB selection by workload |
✅ Resolved & maintained (Day 9 Q5) |
| ACID-C vs CAP-C trap |
✅ Passed on Day 9 Q4 (pre-empting Day 15) |
Weak areas (revisit queue) — none are chronic, only pending re-quiz
| Concept |
Origin |
Severity |
Re-quiz on Days |
Status |
| HTTP statelessness |
Diagnostic Q5 |
High |
4, 11 |
✅ Resolved |
| DNS resolution flow |
Diagnostic Q7 |
Medium |
4 |
✅ Resolved |
| Latency anatomy |
Day 1 Q8 |
Low |
Day 2 |
✅ Addressed |
| Tail-amp |
Day 2/5/6+drill |
Low |
12, 20 |
✅ Resolved |
| Bandwidth vs latency |
Day 2/4/6 |
Low |
20 (maint) |
✅ Resolved |
| JWT vs session cookies |
Day 1/4/7 |
Low |
25 (maint) |
✅ Resolved |
| Bi-directional check for push mechanism |
Day 3/7 |
Low |
28 (maint) |
✅ Resolved |
| Capacity math in architecture answers |
Day 3/6/7/8 |
Low |
12, 14, 18 (maint) |
✅ Resolved |
| L1 cache trade-off recognition |
Day 6→8→9 |
Low |
14 |
✅ Maintained |
| DB trade-off by workload |
Diagnostic Q9 → Day 8 → Day 9 |
Low |
14 (maint) |
✅ Resolved & maintained |
| ACID-C vs CAP-C |
Day 9 Q4 |
Low |
Day 15 (maint) |
✅ Passed pre-emptively |
| Post-mortem structure |
Day 5 Q9 |
Low |
12, 24 |
✅ Consistent (Days 6/7/8/9 Q9 all clean) |
| Slow-start applies with every algorithm |
Day 4 Q4 |
Medium |
11, 25 |
Pending — Day 11 |
| Hot-key mitigation direction |
Day 6 Q8 |
Low |
12 |
Pending |
s-maxage vs max-age in write-up |
Day 7 Q8 |
Low |
14 |
Pending |
| CAP theorem precise reasoning |
Diagnostic Q4 |
Medium |
15, 18 |
Pending — Day 15 |
| Distributed state (rate limiter) |
Diagnostic Q10 |
Medium |
17, 23, 27 |
Pending |
| DNS failover architecture |
Day 1 Q9 |
Low |
15 |
Pending — Day 15 |
| Retry amplification wording |
Day 2/4 |
Medium |
21, 24 |
Pending |
| Anycast + service mesh in global LB designs |
Day 4 Q8 |
Low |
26 |
Pending |
Strengths (confirmed)
- L4/L7 LB fundamentals + all 5 modern LB algorithms
- HTTP status codes, idempotency, statelessness → horizontal scaling
- HTTP caching headers precise semantics
- DNS TTL implications; Anycast BGP vs DNS-based routing
- Little's Law application
- Jeff Dean numbers — all 5 anchors memorized
- Back-of-envelope math including in scenario answers
- Postgres-specific debugging (PgBouncer, pg_stat_statements, VACUUM, autovacuum)
- TCP vs UDP fundamentals + HOL blocking
- Push mechanism selection including bidirectional check
- All 6 cache layers + all 4 write strategies
- Cache-key pollution recognition
- Cascading /healthz trap awareness; sticky sessions decision
- Retry amplification root cause analysis
- Hit-rate math + request vs byte hit rate distinction
- Cache stampede naming + mitigation
- Hot-key problem + mitigations
- CDC scaling pattern
- L1 cache trade-off recognition
- Multi-region cache architecture
- Refresh pattern mapping
- Senior-level post-mortem structure — consistent Days 3/5/6/7/8/9 Q9
- Origin shield / request coalescing / single-flight vocabulary
- JWT vs sessions trade-off precision
- Global CDN architecture design
- DB selection by access pattern (not by scale alone)
- LSM vs B-tree storage engine reasoning
- Chat storage architecture with full capacity math + hot partition mitigation + tiered storage
- Polyglot persistence + migration path
- ANSI isolation level anomaly mapping (Day 9 Q6 — 5/5)
- Write skew recognition and Serializable-only property (Day 9 Q1)
- Read Committed vs Repeatable Read precise semantics (Day 9 Q2)
- Flash-sale atomic conditional UPDATE pattern (Day 9 Q3)
- ACID-C vs CAP-C precision (Day 9 Q4)
- SSI vs 2PL deep vocabulary — "dangerous structures", MVCC, dependency tracking (Day 9 Q7)
- Per-workload isolation-level selection (Day 9 Q8 — Staff-level nuance)
- Ticket-booking architecture with seat-per-row model + soft-hold state machine (Day 9 Q8)
- Defense-in-depth thinking — DB unique constraint as backstop for app logic (Day 9 Q9)
- Lock-contention math with correct units (decrements/sec, not QPS) (Day 9 Q8)
- Composite index leading-column + equality-before-range rule (Day 10 Q1, Q6, Q8)
- Partial index for hot-minority queries (Day 10 Q3, Q8)
- Postgres visibility map + index-only scan mechanics (Day 10 Q7 — Staff-level)
- Partial-predicate immutability trap (
NOW() - breaks partial indexes) (Day 10 Q8 — rare knowledge)
- HOT-update awareness on Postgres storage engine (Day 10 Q8 — Postgres-DBA-level)
- "Sargable" — precise SQL vocabulary (Day 10 Q9)
- Index-cost / write-amp analysis with math (Day 10 Q8)
- 3-clause root-cause post-mortem TL;DR structure (Day 10 Q9)
Daily log
| Day |
Date |
Topic |
Score |
% |
Verdict |
Notes |
| 10 |
2026-08-08 |
Indexing (B-tree, LSM, Hash) |
9.0/9 |
100% |
🎯 PERFECT (3rd in a row) |
Staff-level: visibility map, HOT updates, partial-predicate immutability, sargable |
| 9 |
2026-08-08 |
ACID vs BASE, Isolation Levels |
9.0/9 |
100% |
🎯 PERFECT (2nd in a row) |
Staff-level SSI vocab + per-workload isolation. 6-day gap survived. |
| 8 |
2026-08-02 |
SQL vs NoSQL |
9.0/9 |
100% |
🎯 PERFECT |
Capacity-math gap CLOSED. All chronic gaps resolved. |
| 7 |
2026-08-01 |
Content Delivery Networks |
8.7/9 |
96.7% |
NEW BEST |
JWT + push-dir gaps closed. |
| 6 |
2026-08-01 |
Cache Strategies Deep Dive |
8.65/9 |
96.1% |
Personal best |
Bandwidth/latency & tail-amp gaps closed. |
| — |
2026-07-26 |
Tail-amp drill |
5/5 |
100% |
Gap resolved |
Formula, verify, reverse-solve, recognize, SLA |
| 5 |
2026-07-26 |
Caching Fundamentals |
7.55/9 |
84% |
Strong recovery |
MCQs + Q6 mapping perfect. Q5 tail-amp missed AGAIN. |
| 4 |
2026-07-24 |
Load Balancers deep dive |
5.95/9 |
66% |
Regression day |
3 MCQs + Q6 perfect. 2 T/F traps missed. |
| 3 |
2026-07-22 |
TCP/UDP, WebSockets, SSE, Long Poll |
8.15/9 |
90.6% |
Breakthrough |
+7.6% jump. Strong incident analysis. |
| 2 |
2026-07-22 |
Latency, Throughput & Numbers |
7.5/9 |
83% |
Strong |
Perfect on numbers + Little's Law. |
| 1 |
2026-07-22 |
Client-Server, HTTP, DNS |
7.5/9 |
83% |
Strong |
Perfect on MCQ+T/F. |
| 0 |
2026-07-20 |
Diagnostic |
7.1/10 |
71% |
Baseline |
Right instincts, reasoning depth inconsistent. |