The Cognitive Effort Behind Understanding Code
"I still think that one of the finest tests of programming ability is to hand the programmer about 30 pages of code and see how quickly he can read through and understand it." — Bill Gates
Research indicates that comprehending, modifying, and navigating code demands substantial cognitive resources beyond simply creating new code. Contrary to assumptions, the majority of programming work involves maintaining existing systems, making comprehension a major cost factor in development.
"All programming is maintenance programming, because you are rarely writing original code." — Dave Thomas
Early Research Foundations
IBM Program Understanding Project (1986)
Thomas Corbi's 1989 research found that "more than half of the effort in accomplishing a task for the programmer is towards understanding the system."
Fjeldstad and Hamlen Study (1979)
Research on software maintenance tasks revealed significant time allocation:
Modern Research Validation
Recent studies show these percentages remain consistent or increase:
Developers also spend time mentoring, answering questions from business analysts, and participating in knowledge-sharing activities — all requiring code comprehension.
The Compounding Problem
For organizations running legacy COBOL systems, this cognitive burden is amplified. Decades of modifications, undocumented business rules, and retiring specialists mean every code comprehension task takes longer and costs more than it should.
The question isn't whether your developers spend most of their time understanding code — the research is clear that they do. The question is whether you can give them tools that dramatically reduce that burden.
What Would Your Developers Do with the Time They Save?
COBOL Colleague is purpose-built to address this exact problem — automatically extracting and explaining business functions from complex codebases, turning hours of code archaeology into minutes of clear understanding.