I find this method primitive at best. How do you manage it? Don’t be primitive about it. :-) The serious answer is: use a good logging framework. In particula

I find this method primitive at best. How do you manage it? Don’t be primitive about it. :-) The serious answer is: use a good logging framework. In particular, I’d suggest something that can log at selective levels of information for different parts of your system. If your project’s culture is to instrument your code like this routinely, it can be a very useful asset, and it’s no more disruptive in practice than say adding comments or writing tests. In each case, with experience you get better at judging where to focus your efforts and how much detail is worth including by default, and if that turns out not to be enough you can always add more while you’re working in that area. With modern tools for recording and analysing logs, there is relatively little useful information that you can easily find using a debugger but can’t easily find from good log output. On the other hand, logging has some big advantages: you can capture how your system changes over time, you can record and review concurrent behaviour cleanly, you can capture information from different parts of distributed systems that might be written in different programming languages or running on different devices.