Runtime Panic is my programming notebook after the dust settles. When I spend a few evenings fighting a concept, an API, or a tool until it finally clicks, this is where I try to turn that mess into something readable.

I started writing around 2016 on Medium, mostly about Go. At the time, I was looking for explanations that were beginner-friendly without being hand-wavy, and practical without assuming I already knew the answer. When I could not find enough of them, I started writing my own.

Since then, the topics have expanded: Go, TypeScript, Rust, Web Development, AI tooling, and the occasional thing that looked small until it ate half a weekend. The goal is still the same: start with the reason something matters, build the mental model, and then write enough code for the idea to become real.

I try to avoid two kinds of articles: the ones that explain everything except the useful part, and the ones that drop a wall of code and call it a tutorial. My preferred format is slower, but clearer. We look at the problem first, write a focused example, and then talk through the parts that are easy to miss.

The name Runtime Panic is partly a joke, but it also fits. Most useful learning starts when something breaks at the worst possible time, the error message is unhelpful, and the fix is not obvious. Those moments are annoying. They are also usually where the good explanations come from.

If an article here saves you a few hours, helps a concept click, or at least gives you a better question to ask next, then it did its job.

Uday Hiwarale