>it's a bit naive to say you don't need debugging tools/skills. I didn't say that. >But your stack doesn't end at your code. There's a whole bunch of other co

>it's a bit naive to say you don't need debugging tools/skills. I didn't say that. >But your stack doesn't end at your code. There's a whole bunch of other code yours is linked to, there might be an interpreter or vm, there's the OS, the kernel and firmware. So Good quality code / projects would mean keeping a firm control over all of that stuff, so that when it breaks, it's fairly obvious what caused it (e.g. distinguishing between bugs caused by a different environment and bugs caused by newly pushed code).