One of these days when I get a down moment (which means never) I need to sit down and look at all of the new features in ChatGPT and Claude instead of just using chat for everything.
Ryan R. Rosario retweeted
Distributed Systems series: done.
Added the final 6 articles to the repo today, closing out a series that covers consensus algorithms (Paxos, Raft), replication strategies, consistency models, partitioning, failure detection, and real-world case studies like Dynamo, Cassandra, Spanner, and Kafka.
That brings the repo to 66 articles total.
For anyone new here: it's a GitHub repo where I index every technical article I write, sorted by category so you're not stuck scrolling my timeline to find something. Right now it covers:
HLD (full system design breakdowns: YouTube, Netflix, Spotify, Instagram, Amazon, and more) LLD (parking lots, vending machines, music systems, and other classics) Backend Engineering (APIs, databases, caching, concurrency, security) Distributed Systems (now complete, 9 parts start to finish) Microservices (decomposition, communication, sagas, data ownership) AI (just getting started)
360 stars and counting. If you haven't checked it out:
github.com/harshit3011/Techn…
Running into a Scottish Trumper that parroted the same damn talking points from Fox as in the States was not on my bingo card. I just walked away. Not worth my time. – at Maidens, Scotland
I'm coaching the local mountain biking team: 5th and 6th grade boys. One said "You use a lot of big words." I could stop, but instead, we will make it a vocabulary lesson. They already get a lot of science, geology, geography, physics, botany and meteorology on the trails.
Ryan R. Rosario retweeted
This repo is a goldmine if you are preparing forn Systemd Design Interviews
github.com/liquidslr/system-…
Smelling fire out here in the Eastern Sierra. A message went out to the entire county to evacuate. It was an error. Complete chaos.
From teaching, full time job, mountain biking and gardening, I've been MIA. Is @duckdb still a hot thing?
Ryan R. Rosario retweeted
There is (still) immense value in being the expert on:
databases
performance engineering
benchmarking
distributed systems
Today marks 30 yrs since TWA Flight 800, NYC->Paris w/231 pax on an old 747-100. While I believe the fuel tank theory it's still one of the most bizarre airliner incidents IMO. A lot of weird stuff that night. (My grandfather flew for TWA long ago) newsday.com/long-island/hist…
Sadly, I think I am done with @VirginAtlantic . For one, they keep switching our aircraft and then we have to re-select seats. Second, the difference in Premium Economy between the B787-9 and the A330-900neo is awful and we have to pay the same price. It's highway robbery.
In this past 8 yrs at Google, I've changed a lot as a person.
• I learned to prioritize work/life balance.
• I transformed how I communicate and collaborate.
• I learned to manage stress effectively.
• I focused on my health and lost a lot of weight (last photo is 2026)
Good. Riddance. He always seemed like a plant - a saboteur. My autistic feelers knew he was sleazy even before the Nazi tattoo. He voted for Trump 2x and Collins 3x and called himself a Communist, FFS. Did Democrats/voters really need to wait this long to force him out? Come on!
I forgot how terrifying and slow old mechanical hard disks are on large workloads. It's almost as terrifying as a dial up modem.
Looks like I am covering the right material.
Most backend interview questions eventually lead to one of these
• REST
• gRPC
• OAuth
• Redis
• Kafka
• Idempotency
• Message Queues
• CDN
• Rate Limiting
• Load Balancers
• Database Indexing
• Sharding
• Replication
• Circuit Breakers
• Webhooks
• Connection Pooling
• Observability
Save this before your next backend interview 📌
Caching caching caching!!!!
If you're a backend engineer,
Please learn :
- SOLID design principles
- Multithreading
- Immutability
- Streaming , messaging
- Caching
- Idempotency
- Security
- SSL, JWT, OAuth
- factory, decorator, singleton, obeservable design patterns
- TDD
Invest in the concepts—they'll pay dividends throughout your career.
Ryan R. Rosario retweeted
Microservices should talk to each other only via queues. If a microservice failure leads to your system failure, you’re doing it wrong.
If you don’t have the skills to design such a system, make a monolith.
And if you can’t design a scalable monolith, read a fucking book.
















