Today's idea is a good call graph navigator. See which functions call which other functions, but in a way that's not an overwhelming tangled mess, even if your code is. First we look at some examples of existing tools, and I explain some of the problems I see in them, and then I show my ideas.
Existing tools mentioned in the video:
https://www.doxygen.nl/
https://www.gnu.org/software/cflow/
http://www.gson.org/egypt/
https://github.com/petersenna/codeviz
https://sourceforge.net/projects/tceetree/
https://visualstudio.microsoft.com/
https://www.scitools.com/
As a programmer with 20 years of professional experience, I've always wished for better text editors, compilers, integrated development environments, version control systems, build systems, and so on. This video series presents a vision for future tools. Playlist with all episodes released so far: https://youtube.com/playlist?list=PL4idJHFfKXwOz8bc6eOun-QzSzkj6Aj_y
Butterfly image by Hebi B. from Pixabay, https://pixabay.com/users/422737-422737/?utm_source=link-attribution&utm_medium=referral&utm_campaign=image&utm_content=658047
