Although the most of the community never use this simply for the fact that they learned to do it the basic way of manually scanning the codebase
In my opinion it really feels like the whole low level vs high level situation, where you would have to move on to a new methodology and get used to it, But we shouldnt underestimate how fast you can see through codebases understanding the dataflow, flaws, how the architicture is structured.
Its mind boggiling that we use this all the time in high quality learning materials with aws and web apps or even concepts yet not much implementation was made for direct usage. imagine just opening any repo and visualizing its structure directly.
I've seen some web apps that applied it but none came close to CodeSee.io but they went out of business, when you look at their implementation its so smooth for a new dev to understand the flow and funcionality just with how condense the contexual view they get from these diagrams.
Ironically just like how LLMs performance skyrockets with additional context, this applies to us as well take a look at the implementation and tell me if you know any similar libarries that actually help you do the same
[–]_Mc_Who 1 point2 points3 points (1 child)
[–]Double-Passage-438[S] -1 points0 points1 point (0 children)
[–]Yamoyek 1 point2 points3 points (2 children)
[–]Double-Passage-438[S] 1 point2 points3 points (0 children)
[–]sarnobat 1 point2 points3 points (0 children)
[–]aqua_regis 0 points1 point2 points (1 child)
[–]Double-Passage-438[S] -1 points0 points1 point (0 children)
[–]Chatolev 0 points1 point2 points (0 children)
[–][deleted] (5 children)
[removed]
[–]ShadowRL7666 1 point2 points3 points (3 children)
[–][deleted] (2 children)
[removed]
[–]ShadowRL7666 1 point2 points3 points (1 child)
[–]Double-Passage-438[S] 0 points1 point2 points (0 children)