Debugging. I've sunk a lot of time into trying to change this. Among other changes, I've: - Improved crash dump collection, to spend less time reproducing bu

Debugging. I've sunk a lot of time into trying to change this. Among other changes, I've: - Improved crash dump collection, to spend less time reproducing bugs and be more thorough in addressing them. - Improved code debuggability - for example, writing scripts to inject call stack information into actionscript and java via disassembly, which I can then display on assert, especially on platforms where I have unreliable or incomplete debuggers. - Learn and use defensive coding techniques to make bugs fewer in number, shallow, and caught more quickly and with more context. - Write thorough tests to catch said bugs before I even run my main application, and more edge cases to input - Learned more tools to catch bugs I might not even know exist - valgrind, address sanitizer, static analyzers, fuzz testers, ... I spend much less time debugging my own code now. If I'm lucky, I'll work on projects where I don't have to debug my coworker's code all that much either. That still leaves debugging 3rd party libraries and tools - which I may lack the source to entirely - that I suddenly have more free time to really properly investigate and get to the root cause of.