@allison @idiot @animeirl @nishi I don't think it's like that, I think some tools are not very useful. You can see what a process did or you can understand how the program works. This is the reason "the code doesn't resemble the compiler's output" is horrifying: you can't understand how the program works by reading the code if the compiler editorializes. So you bash stuff in at one end, the compiler does something completely different (e.g., the stuff in the top post in the thread), then at the other end you can use a debugger: this is a worse method of programming than thinking about the problem, writing code to express an algorithm, and then fixing your understanding if you fucked up the first step or fixing the code if you fucked up the second step.