“A common fallacy is to assume authors of incomprehensible code will be able to express themselves clearly in comments.” – Kevlin Henney TLDR Clear writing equals thinking. Since you want your programmers…
Category: Programming Practices
Scoping a Refactoring Effort for My Boss
TLDR You’ve been asked to consider replacing 2 open source modules–here is how to use Understand’s Architectures and Dependency analysis to let your boss know how much effort/risk this will entail. Details…
Virtually Execute Code with Understand
Abstract: A script for virtually executing code. A debugger inside Understand sure would be nice. I hope I’m not the only one out there who uses Understand while debugging. Integrating a debugger…
Share (Or Don’t)
There are a lot of benefits to sharing Understand projects, but if you want to create your own, you can still benefit from the shared knowledge of your team.
The Perfect Catch
Understand’s CodeCheck features let your team catch bugs before they even make it to QA and help keep your code readable and maintainable.
Short-term memory overload while debugging
The decisions you make while thinking about code are far too complicated to trust to memory. Ken shows how Understand helps you not rely on short term memory and walk code in an organized fashion that misses nothing.
Our Favorite Computer Science Quotations
An ever growing list of quotations about computer science, with an emphasis on software maintenance
Why use Understand? (Dinner Party edition)
A long, and growing, list of dinner party conversation reasons Ken gives for why customers use Understand.
Blame Can Be Good
A bug in the control flow graph is solved using the Git blame margin in Understand to quickly find a related fix in a recent commit.
The Science of Debugging
The process of debugging is equivalent to the scientific method – a set of principles that apply equally well to debugging as to scientific inquiry.