Debugging TypeScript Applications is in print
My first book “Debugging TypeScript Applications” is out in print!
Buy e-book directly from Pragmatic Programmers.
Buy paperback from:
Or email me, especially if you are in Europe. I might have a signed copy for you.
I wrote this book to fill the knowledge gap. Your typical work as a software engineer is rarely writing code, but much more often, it’s figuring out how a system works and finding mismatches between what you want it to do and what it actually does. It’s setting up experiments as if you were a scientist discovering the laws of physics in this little universe that is your software. More so if you’re collaborating with many different people. Even more if you work on a large project with a lot of legacy code. More if you’re into AI-assisted or agentic coding. The ease of writing new code makes the skill of getting it to work correctly even more precious.
Debugging is a craft of its own, and we’ve got neat tools at hand. We’ve got proven, battle-tested methodologies to catch issues, prioritize them against other product work and other issues, find root causes, reliably solve and verify the solutions, making them impossible to reoccur. But unlike software architecture, languages, frameworks, or new APIs, these skills didn’t enjoy enough attention in literature, especially given how valuable they are.
I am proud of this book and grateful to all the people who helped me in the process. Let me know if you like it (or not)!