Assuming you have more work than resources (which is what one should plan for) I would find it hard to sacrifice the 'strategy' aspect of bug tracking systems.

Assuming you have more work than resources (which is what one should plan for) I would find it hard to sacrifice the 'strategy' aspect of bug tracking systems. A good bug tracking system allows you to balance quick/low-overhead logging with an ability to create categorical data points that let you analyze your work & workload. Having this data collection & reporting allows you to identify & trend problem areas that can not be seen looking at a single bug at a time by different people. It also allows you collect similar/overlapping areas of work to strategically manage your resources and productivity - saving you time and money. Maybe the case is that the article comes from a company that's just too small to realize the benefits of planning.