01
Mechanized Comprehension
How large-scale software systems can be understood through tooling that extracts meaning, structure, and intent from code at scale.
Legacy Code Labs · Est. 2024 · Research since 2019
Tooling, experiments, and research to systematically understand and evolve codebases in the AI-era.
The work is organized around four themes that emerged from years of building tools and applying them in real-world engagements.
01
How large-scale software systems can be understood through tooling that extracts meaning, structure, and intent from code at scale.
02
How correctness and gaps in evolving software can be identified systematically through autonomous analysis.
03
How problems, once identified, can be addressed through targeted, tool-assisted intervention rather than costly rewrites.
04
How codebases can be intentionally steered toward better states through continuous, guided transformation, not accidental drift.
Open source tools born from real engagements. Each one built to solve a problem that manual approaches couldn't.
A software design tool for AI-native developers and coding agents. Review design impact before commit.
Verification
Visualizes the structure of large Kotlin and Java classes as interactive graphs. A 3,000-line class on one screen, updating in real-time.
Comprehension
Structural analysis of Android codebases through graph queries via jQAssistant.
Comprehension
Leverages Git history to reveal tribal knowledge. Every codebase has a story in its version control. Timelapse makes it legible.
Comprehension
February 20, 2017: I picked up Michael Feathers' Working Effectively with Legacy Code while struggling with a codebase I couldn't make sense of. By 2019, I was building tools to solve it. What once took nine months to earn, a team's trust, collapsed to two or three days.
Read the full storyPapers, tools, and open source releases from the lab.
Feathers wrote the book that named the problem.
We're building the tools that solve it.