The devil is in the details. You have to understand what the tool does, how it installs, and if it costs money, lordy you have to wait for it to be approved by

The devil is in the details. You have to understand what the tool does, how it installs, and if it costs money, lordy you have to wait for it to be approved by 10 levels of management. Another problem is that log indexers and the aforementioned Azure insights almost certainly would require boatloads of storage and processing costs. Programmer time is fundamentally disrespected in organizations, and debugging/QA is even moreso. Companies basically throw a laptop at both of them and say "good luck with whatever free tools are out there". But your example was basically a stack trace, from Javaland, I wouldn't call it revolutionary in tooling and is ground-level features of Javaland IDEs for about a decade or more, but maybe C#/whatever is different. I won't disagree with the core point, since I complained about a lack of visualization tooling for multithreaded apps above. We need more tools and tooling awareness.