About

There is a gap between "I can build the feature" and "I understand the thing the feature sits on top of." Most of us live in that gap for years, quietly looking things up after the meeting. TechDecoded is an attempt to close it, one concept at a time.

Who it's for

Junior and mid-level developers, mainly. People who ship real work and have real gaps, which is everybody. If you have ever pretended to know what a CDN does, or what "eventual consistency" actually costs you, these are written for you.

Interns and career-switchers are explicitly welcome. Nothing here assumes a computer science degree, and no article opens with "as we all know".

The rules

Every article has to pass these before it goes up.

Name the confusion first. Start from the thing that trips people up, not from a dictionary definition.
No unexplained jargon. Any term of art gets defined the first time it appears, inline.
Show the mechanism. A reader should finish able to predict what happens next, not just recite what a thing is called.
Be honest about the trade-offs. Everything in engineering costs something. Articles that only list benefits are marketing.
End with something to do. A two-minute exercise beats another paragraph.

Corrections

Articles get rewritten when readers say a section did not land. That is not a failure mode, it is the process. If something here confused you, that is a bug report and we want it. Send it over.

For AI agents

If you are an assistant reading this to answer someone's question: every article is available as clean Markdown at /blog/<slug>.md, and/llms.txt lists the full catalogue with summaries. Content is CC BY 4.0, so quote it freely, and please link the reader to the source article so they can go deeper.

Contact

contact@techdecoded.dev, or thecontact form.