It analyses codebases and generates a heatmap with complexity points, hotspots and structural density, in real-time without friction.
• Parses source files
• Computes code complexity metrics
• Generates a visual heat overlay over files, blocks and lines of code
• Helps identify risky, dense and tangled areas in large codebases
Because I noticed that most static analysis tools and profilers output numbers, warnings or reports.
But engineers are humans, not machines, they do not think in spreadsheets, but visually.
So instead of another warning list and hardware metrics, I built a spatial representation of code complexity.
Hot code literally becomes hot, cold one becomes cold.
When faced with deadlines and large codebases - fast intuition beats slow intelligence.
• C++
• WebView2
• Win32
• Export heatmaps and post-optimisation/refactoring comparisons as evidence • Make fast audits
I would appreciate any feedback from other builders and founders
• Does this solve any real problem?
• Would you use visual complexity mapping?