Satendra

I had a my interview with a senior engineer from Australia During the interview he asked me to write a piece of code that solves a specific problem ... the core problem was to implement a R/W consistency with Spanner style true time intervals where reads will be waiting until local clock uncertainty interval excludes uncommitted writes some todos I had to complete >> the program should have a truetime interval per node in redis which will be updating via ZADD with interval width as score >> Read waits until TT[.]now().earliest > write_timestamp.latest using Redis pub/sub coordination the video doen't contains much it was all about the code and the workflow it follows

Hey chat if you want to deep dive into kafka you should be going ahead with this github repository it literally has everything from fundamentals to how big orgs uses kafka github.com/pmoskovi/kafka…

Made a repository to dump down all my learnings related to go and minio found out that chapter wise thingy is really effective and helps to break down everything and just gradually increase the complexity github.com/mrinalxdev/gom…

Go (Golang) Roadmap for Backend Engineers, Who Want to Ship Fast: 1. Master the Basics : Syntax, variables, loops, functions, packages & modules 2. Understand Go’s Real Power : Structs, interfaces, composition & embedding 3. Master Pointers : Learn how they work, when to use them, and why they matter 4. Goroutines & Channels : The real reason people choose Go → master concurrency here 5. Error Handling : Learn proper error wrapping, custom errors & context 6. Build CLI Tools : Use → flag, cobra or urfave/cli, make something useful 7. Work with Data : Files, JSON, YAML, HTTP clients & basic APIs 8. Build REST APIs : Use Gin or Fiber + proper routing, middleware & validation 9. Advanced Concurrency : Worker pools, pipelines, fan-in/fan-out, rate limiting 10. Database Layer : PostgreSQL + GORM or sqlx + proper connection pooling 11. Testing & Quality : Unit tests, table tests, benchmarks & integration tests 12. Production Ready : Docker, logging, graceful shutdown, config management, observability Bonus Steps: - Read Go source code of popular packages - Build 3 real projects (Auth service, Background worker, Scraper) Stop just “learning Go” Follow this → become → production dangerous Save it. Follow it. Ship it. Who’s starting this journey in 2026?

System Design roadmap !! Start → Basics → Networking → OS → Databases → Caching → Messaging → Scaling → Reliability → Security → Observability → Practice Requirements → APIs → Load Balancer → App Servers → Database → Cache → Queue → Storage → CDN → Rate Limiter → Monitoring Client → DNS → CDN → Reverse Proxy → Service → DB → Cache Latency → Throughput → Availability → Consistency → Durability → Fault Tolerance → Scalability SQL → NoSQL → Indexing → Replication → Sharding → Partitioning → Transactions REST → gRPC → WebSockets → Async Processing → Event-Driven Systems Redis → Kafka → RabbitMQ → S3 → Postgres → Elasticsearch Single Node → Distributed → Multi-AZ → Multi-Region Monolith → Modular Monolith → Microservices only when needed Logs → Metrics → Tracing → Alerts → SLOs Brute force design → Bottleneck finding → Tradeoff thinking → Better architecture Functional requirements → Non-functional requirements → Capacity estimation → High level design → Deep dive → Failure cases → Scale plan Read designs → Watch failures → Build small systems → Review mistakes → Redesign again URL Shortener → Rate Limiter → Chat App → Notification System → Search → Feed → Payment System → Ride Sharing Think → Draw → Explain → Defend tradeoffs → Improve Consistency → Clarity → Repetition → Deep work End → Crack interviews and build real systems Save this !!

After multiple senior backend interviews, I realized something. There’re high chances of cracking the interview if you’ve actually implemented the systems, and not just read about them. Next 10 days, implement these with the help of your favourite LLM. 1. Feature Flag System Interfaces, rules engine, extensibility. 2. Retry + Backoff Library Strategy pattern, pluggable policies. 3. Notification Routing System Channels, priorities, templates. 4. Rate Limiter Algorithms, abstractions, thread safety. 5. Circuit Breaker States, transitions, failure thresholds. 6. Metrics Aggregator Time windows, aggregation logic, concurrency. 7. Configuration Manager Versioning, caching, listeners. 8. Payment Processing Flow State machines, idempotency, validations. 9. Cache Library Eviction policies, extensible storage. 10. Job Scheduler Workers, queues, retries, priorities. Check my pinned post for the resources to learn these.

feels soo good the repository went up from 30 stars to 80+ stars after this post You can literally learn a ton from github but the question is are you willing to put in some time to search ¯\_(ツ)_/¯

The best book for 2026 is available as an open source Google doc thanks to @justinskycak: docs.google.com/document/d/17q… If you don't get motivated or inspired within two chapters, you're ngmi.

This playlist explains Microservices like no one else does

You can use this article to learn about docker compose I know its a 2022 article but clears most of the foundation to just start building with it docker.com/blog/using-awe…

Yesterday, I just finished "Surrounded by Idiots", and it is something I would recommend every tech lead and manager read. Even if you are not one, you should still skim it - it helps you understand the people around you. The book talks about and breaks down personalities into four types, each with distinct traits. You read it and immediately start recognizing yourself and others. It covers: - how each personality is - how to work with them - how they take feedback - how they handle stress - which personalities are compatible For anyone in a leadership role, this is genuinely valuable. Can't recommend enough. Knowing that your quietest team member is not uninterested but is processing information internally. You stop treating everyone the same, and your team responds better. It also helps you build the right team. Some personality combinations create friction, while others naturally complement each other. Understanding this helps you structure teams better and maximize outcomes. By the way, even if you are not managing anyone, it helps you understand yourself - why you communicate the way you do, what actually drains you, and why certain people feel difficult to work with. Worth reading if you lead people. Worth skimming if you work with them. Linked below.

Just tried System Design Lab by Sumit Suman ,this is seriously impressive A fully interactive platform (no signup!) covering everything from OOP & design patterns to distributed systems, with simulations, mock interviews, and even a "System Architect Survival" game based on real outages. Hands-on > passive learning. This is how system design should be taught. systemdesignlab.netlify.app Great work building something genuinely useful for the community 🚀

Wrote a blog on search engine at scale, link in comments :)

It was a good read on database sharding pingcap.com/blog/database-…

1/ Most people “prepare for interviews”. If you’re aiming for top spots like @Rippling , @databricks , @stripe , @nvidia , @Razorpay , @JioHotstar etc, you may need to rebuild yourself for that bar. Here’s the PLAYBOOK for 0–5 YOE folks in India. Save this. 🔖

🚨 Someone just made a video on how to handle 1 MILLION Request per second.

This is my assignment for a Hong Kong based startup for Backend Engineer role In the interview we discussed on how to build scalable Multi upload function for large files and how do we generate presigned urls for short time ... Doubled down on building the presigned function and here it is what I built for now it can view presigned urls asset and download those from the bucket, its a really simple implementation of what large video recording system have in their main infrastructure ... built with go, minio, psql and simple html

A Russian guy has discovered a method to learn anything ten times faster using AI! It involves NotebookLM, Gemini and Obsidian.

STUDY HARD. No matter if it seems impossible. No matter if it takes time. Wake up early and start studying for your future. Just remember that the feeling of success is the best feeling in the world.

I'm not 100% happy with the quality of code claude or codex generate. Theres a lot I discard or go back and finesse the low level architecture. Also at work I'm seeing too many problems arising out of people abdicating critical taste and judgement calls to the LLMs. But that said my extensive use of agentic engineering both at work and personal side projects has brought a lot of learnings on how to effectively write code via agents. This is a collection of those learnings.