An Interview with Brian Kernighan (2000)
cs.cmu.edu
cs.cmu.edu
> we make a lot of progress, we are able to undertake bigger projects, we can build things which are much more interesting and sophisticated than what we could do 10 years ago. [...] But the amount of messy, intricate, awful code that doesn't work very well and that's underneath all of that has also increased enormously. In some sense I guess we'll continue to make progress, but it'll always be kind-of grimy and not-really-done yet. Because people always take on more than they can reasonably handle, they're always overreaching, and they seem never to go back and clean up the stuff that they did before.
Ha! Who would've thought that the author of so many books on software engineering prefers using print statements for debugging. Great interview!
>The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.
However the previous sentence is:
>The debugger adb is useful for digging through the dead bodies of C programs, but is rather hard to learn to use effectively.
https://news.ycombinator.com/item?id=10080956
Notice that since then, the rest of that video interview has been posted:
An algorithm being a standard fare at job interviews looks to be on the bottom of such an accomplishment pile.