Dario Amodei: we must slow down Sam Altman: we agree Elon Musk: Dario is right All of this looks fishy. What is cooking up ? 🧐

The truth is that the engineer who uses AI to move 10x faster will eventually compete with the engineer who refuses to use it.

The truth is that system design becomes easy when you stop memorizing diagrams and start understanding trade-offs.

Thanks @parthratra12, really glad the HLD posts have been useful 🙌 For interview prep specifically, this combo is what I’d recommend: @_hellointerview — closest thing to a structured course. Guided practice on common problems, the interview loop (reqs → API → HLD → deep dives), and feedback. Start here if you want interview-shaped practice. System Design Interview: An Insider’s Guide — Vol 1 & 2 (Alex Xu @alexxubyte ) — best for pattern recognition. Repeatable 4-step framework + lots of diagrams + classic questions (rate limiter, unique ID, news feed, YouTube, payments, etc.). Designing Data-Intensive Applications (Martin Kleppmann) — not an interview book, but the one that actually builds intuition on storage, replication, partitioning, and consistency. Use it after the patterns click, so you can defend trade-offs instead of just naming components. Order that works well: Hello Interview / Alex Xu first → DDIA in parallel or right after for the “why.”

4 weeks of #30DaysOfJava done 💪 28 concepts still going week 5 coming up: → Kafka with Java → Spring Security internals → JPA/Hibernate deep dive → Testing best practices → Real world architecture decisions the stuff that actually matters in senior engineering roles follow along 👇 #Java #SoftwareEngineering #30DaysOfJava

System Design Interview: Your database already has backups. So why do you still need database replication? What problem does replication solve that backups don't?

You can keep only 3. You must fire 1. -Strong Consistency -Eventual Consistency -Transactions -Distributed Locks Which one are you firing and why?

week 4 honest reflection: most underrated topic: Java Memory Model nobody reads the spec everyone suffers the bugs most exciting topic: Virtual Threads (Java 21) this genuinely changes how we write backend Java most common production issue: N+1 queries seen it in every codebase without exception what was your week 4 highlight? drop below 👇 #Java #30DaysOfJava

The truth is that your 5 years of experience mean nothing if you've done the same job 5 times.

The uncomfortable truth: AI won't replace most software engineers. It will make mediocre engineers much easier to replace.

The truth is that engineers who can explain complex systems simply are rare.

AI coding agents are amazing. Until you ask “why did you change these 47 files?”

Day 28 of #30DaysOfJava — week 4 done ✅ covered this week: → Concurrency — locks, deadlocks, tools → Java Memory Model — happens-before → CompletableFuture — async done right → Microservices Patterns — circuit breaker, saga → Performance Tuning — N+1, GC, profiling → Java 17+ — records, virtual threads week 5 starts tomorrow #Java #30DaysOfJava

The engineer making ₹30L who keeps learning will eventually beat the engineer making ₹60L who stopped learning.