[nebucnaut]

Actually I started this question to hear some oppinions, not to advertize a certain tool, but I'll answer you anyways. I'm one of the makers of Coati (http://www.coati.io/) and I'm using that tool quite extensively. I don't wanna say that it's perfect and everyone should use it (at least not in this Ask HN), because I want this to be a more general discussion ;)

[detaro]

Ok.

To expand on my answer above a bit, a few categories of tools I've (superficially) looked at or see others work on:

Code to UML (and the other way around): Generally have been clunky to use, and can't distinguish between important/non-important things. Might be useful for larger domain models, but that hasn't come up much for me.

Overview tools: typically generate a treemap of some sort from code directories and/or commit history. I can see how they might be useful to find specific hotspots in really large code bases, but I'm not so sure if that is a thing that's actually needed all that often (I certainly haven't)

Projectional editors are related and are interesting, but also don't feel all that practical. Incredibly hard to get right.

What I'm missing in the field: graphical debugging tools that e.g. visualize a run-time object graph, plot values/events, ...

[supercheetah]

> What I'm missing in the field: graphical debugging tools that e.g. visualize a run-time object graph, plot values/events, ...

GNU DDD does this really well, but it's unfortunately limited to just C/C++, and it still uses its old clunky Motif interface.

[grif-fin]

"What I'm missing in the field: graphical debugging tools that e.g. visualize a run-time object graph, plot values/events, ..."

Have gone through the same thought route. Very much agree.