Hi, I'm Ajith.

I build backend systems for a living and write down what breaks. This site is where those write-ups live: plain accounts of real problems, for engineers and for anyone curious how software actually fails.

media.ajithakdev.com

Ajith Kumar Karudasevai

Backend Engineer

  • Node.js
  • TypeScript
  • MongoDB
  • AWS
  • Linux
  • AI tooling
based in
Bengaluru, India
write-ups
7
handle
@ajithakdev

What happens here

I write

Incident-style write-ups: one real problem, the guesses that were wrong, the actual cause, the fix, and how to spot it faster next time.

Read the articles →

I build

Backend systems for a living: Node.js and TypeScript services, MongoDB and DocumentDB, AWS, and the Linux boxes underneath them.

See my work →

I share

Short versions of the same lessons, plus practical notes on AI tools, on Instagram. Made for people who have five minutes, not fifty.

@theajithakdev →

I learn in public

If I have not run into it myself, I do not write about it as if I had. The posts show the dead ends too, because that is where the learning is.

Browse by topic →

How a post is made

  1. Something breaks

    A sign-in hangs. A query returns numbers that look right and are not. A tunnel stops carrying traffic.

  2. Wrong guesses

    I write down each hypothesis, what it predicted, and what ruled it out. Most of them are wrong.

  3. The actual cause

    One observation does not fit. Following it leads to the mechanism, with a command that proves it.

  4. The write-up

    Generalized, stripped of anything private, and published so the next person finds it in a search.

What you will not find here

No sponsored posts.

No invented numbers.

No tracking cookies.

Confidentiality standard

I write from real work, so every post is generalized before it goes up. Examples use synthetic data, placeholder domains, and documentation IP ranges.

  • neverPrivate organization architectures, proprietary workflows, or internal system designs.
  • neverInternal hostnames, IP addresses, domains, ticket IDs, request IDs, or database schemas.
  • neverCustomer records, patient or healthcare identifiers, or client names.
  • neverUnredacted production logs, internal traces, or infrastructure credentials.

Say hello.

Questions about a post, a correction, or an idea for one: any of these reach me. The contact page on my main site is the surest.