Random user

How to actually get good at backend systems. It's slow. But it works. 1. Pick one thing you already use every day. Postgres, Redis, Kafka, whatever your job runs on. 2. Go one level deeper than you are right now. If you write queries, learn to read query plans. If you can read plans, learn how indexes actually sit on disk. Know that already? Go learn what VACUUM is doing. 3. Break it on your laptop. Fill up the disk. Kill a replica. Leave a transaction open and watch the table grow. Breaking it once beats reading about it ten times. 4. Explain it to one person on your team. If you can't explain it simply, you don't get it yet. Then go one more level down. Background loop you should keep running: whenever something weird happens at work, a slow query, a random spike, a flaky test, chase it till you know the real reason. Most people stop at "restarted it, it's fine now." The ones who keep digging are the ones who get good. Stuff that gets in the way: "I'll do another system design course" → courses teach you the words. They can't give you that moment where your own test fails in a way you didn't expect. That's where you learn. "I've read DDIA, I know distributed systems" → cool, now pick one chapter and make that failure happen on your machine. Then you know it. "We're on managed services, I don't need internals" → managed stuff breaks too, you just get less info when it does. The person who knows what's underneath fixes it while everyone else refreshes the AWS status page. "I'll get to it when work calms down" → it won't calm down. Thirty minutes a day beats the free weekend that never shows up.