4 ms·
> Tooling/Perf/etc is not needed when running (do you really want to debug in production) Do I want to debug in production? No. Do I have to do it anyways? Al
by ori_b 7y ago
> Tooling/Perf/etc is not needed when running (do you really want to debug in production)
Do I want to debug in production? No.
Do I have to do it anyways? All the fucking time. I'm not perfect, I sometimes ship bugs, and when they show up in production, I need to diagnose, determine if rolling back will solve them, or whether I need to fix forward and how. Not being able to debug in production is simply unacceptable.
I want to ship perfect code. But I don't. So, instead, I debug. If the issue shows up in production, I debug in production.
- mirceal 7y agoyeah no. you don’t debug in production. you have logs and metrics. if you need to debug (as in attaching the debugger) you already are in trouble
- ori_b 7y agoOf course I'm in already in trouble. That's why I'm debugging. I tend not to debug things that are working perfectly. If I can't attach a profiler to find, for example, the code that contains a regex that's doing too much backtracking with production data, then I'm dead in the water. If I can't get a sample out of a system that's received a query of death, then I'm dead in the water. If I can't attach dtrace (or the equivalent) and get stats on how much I/O a system is doing in response to various events, I'm dead in the water. Being able to dive into the depths of a system is the #1 criteria for confidently being able to put it into production.