Skip to main content

Blog — Page 3

RSC After Six Months: What Surprised Me MostServer Components change how you think about the network boundary. Six months in, here's what still catches me off guard.
reactjavascript
2m
What On-Call Fatigue Taught Me About System DesignAfter a particularly bad on-call week, I realized the alerts were the symptom, not the problem. The system needed redesign, not more monitoring.
careerreflection
1m
What I Learned From 'Staff Engineer' by Will LarsonThe Staff Engineer title doesn't come with a playbook. Larson's book collects org patterns from real staff-plus engineers at tech companies.
book-notescareer
1m
Designing API Rate Limits: Token Bucket vs Sliding WindowToken bucket is simple. Sliding window is fair. Here's the trade-off we made and why we ended up keeping both.
system-designperformance
1m
Shaving 200MB Off Our Docker Image With Multi-Stage BuildsOur Go binary was 18MB, but the image was 1.2GB. Multi-stage builds brought it to 22MB. Here's the exact Dockerfile.
dockergo
1m
Slashing CI Times With Smart Caching in GitHub ActionsOur CI was taking 12 minutes per push. Caching dependencies and build artifacts brought it to 3 minutes. Here's the cache-key strategy.
ci-cdjavascript
1m
Tuning PgBouncer for a Read-Heavy APIWe cut p99 query latency by 40% just by changing three PgBouncer settings. Here's the before and after.
postgresqlperformance
1m
A Circuit Breaker Implementation in Go That Saved Our UptimeWhen a downstream dependency started failing, the circuit breaker pattern prevented cascading failures across three services.
gosystem-design
1m
Why I Started Writing in Public (and What Changed)Writing in public forces clarity. After six months, I understand topics better, get feedback faster, and have a searchable reference of what I've learned.
careerreflection
1m
One Index That Fixed a 5-Second QueryA dashboard query was timing out. EXPLAIN ANALYZE showed a sequential scan on a 2M-row table. One index brought it to 8ms.
sqlpostgresql
1m