Sitemap
Medium Logo

I’m a backend engineer and SDE III working mostly on the unglamorous half of distributed systems: queues, retries, timeouts, failure modes, and the things that page you at 3am because someone changed a configuration.

I write anonymously because some of the most useful engineering lessons come from things you can’t easily write about with your name attached: outages I caused, interview loops that made no sense, production failures, and the uncomfortable question of what AI is actually changing about software engineering.

What you’ll find here:

* Distributed systems: system design with the trade-offs, failure modes, and operational pain left in.

* DSA & interviews: problems from real interview loops, with the reasoning behind the solution rather than just the final code.

* Engineering careers: practical writing for engineers, especially people trying to break into the industry in India while most career advice is still five years out of date.

* AI & software engineering: what changes when AI writes a significant part of the code and engineers have to become much better at reviewing, validating, and operating it.

I’m currently building two services around that last problem. One analyzes code before deployment and looks for patterns associated with real-world outages. The other connects incidents back to what was deployed and helps identify the change most likely responsible, so on-call can revert or fix it instead of bisecting deployments at 3am.

There’s real ML involved, but it’s less magical than it sounds. Mostly, it’s a data problem.

Comments are open. I read them.

Connect with The Abstract Engineer
The Abstract Engineer

The Abstract Engineer

Backend engineer, SDE III. Distributed systems, DSA problems from real interview loops, and too many opinions about AI. No name here on purpose.