Hacker News new | ask | show | jobs
by Izkata 925 days ago
I did this by adding every SQL query to a new log file (only active in development), then tailing it while developing. Not only is 1+N very visible as a long string of the same query over and over, it also lets you see in real time when there's a long pause from a query taking longer than expected.

Also we often had something that was more like 1+3N, basically a 1+N problem but it was looping through the same 3 queries over and over.