About theweekenddev

I started this blog because I kept running into the same problem.

I would use something at work (JWT, Redis, a load balancer) and realise I could not explain how it actually worked if someone asked me. I knew enough to get the job done but not enough to really understand what was happening underneath. That gap bothered me more the longer I was in the industry.

So I started writing things down. Not as tutorials. Not as documentation. Just as explanations I would have wanted when I was first figuring this stuff out. Clear, honest, without the hand-waving that most articles get away with.

That is what this site is.

What you will find here

Tech Explainers are deep dives into the concepts behind the tools every backend developer uses. How JWT actually works, why consistent hashing exists, what Docker is doing at the kernel level. Not how to install them. How they work.

Low Level Design covers the class-level design problems that come up in interviews and in real codebases. Parking lots, rate limiters, food delivery systems. The focus is always on the thinking behind the design, not just the final diagram.

SDE Playbook is the interview prep section. DSA patterns, system design breakdowns, career guides. Written for developers who want to understand patterns, not just memorise solutions.

Why "the weekend dev"

Honestly, that is when most of this gets written. Not because I only care about this stuff on weekends, but because the weekend is when I have time to sit with something long enough to actually understand it. During the week there is always a ticket to close or a meeting to join. Saturday morning with coffee is when the thinking actually happens.

The name also reflects the audience I had in mind. Working developers. People with jobs and responsibilities who still want to keep learning and getting better at what they do. Not students cramming for an exam, not fresh bootcamp graduates. Engineers who have been around for a bit and want to go deeper.

A note on quality

Every post on this site gets written once I feel like I actually understand the topic well enough to explain it clearly. That means the publishing cadence is slow sometimes. I would rather put out one genuinely useful post than three that are just filler.

If something here helped you, I genuinely want to know. And if something is wrong or unclear, I especially want to know that.

You can reach me at hello@theweekenddev.com.