Get the latest tech news
Clean Code vs. A Philosophy Of Software Design
A discussion between John Ousterhout and Robert Martin about differences between John's book "A Philosophy of Software Design" and Bob's book "Clean Code". - johnousterh...
In a project of any size, I think your approach would result in developers spending large amounts of time reading code to re-derive the interfaces, and probably making mistakes along the way. I'm not convinced by your argument that there's less debugging because "you just saw everything working a minute ago": it's easy to make a tiny change that exposes a really gnarly bug that has existed for a long time but hasn't yet been triggered. Similarly, the Clean Code position on TDD is one-sided, failing to recognize any possible weakness and encouraging readers to take this to a tactical extreme where design is completely squeezed out of the development process.
Or read this on Hacker News
