re: What is your debugging approach? VIEW POST


Go into the logs, get all the data as they were at that point in time, throw them in a pot, boil them into a few unit tests...and see why that problems occurred.

The problem is that the project I am currently working on, as weird as it may seem, it has so many time sensitive external dependencies. So that it doesn't even make sense to even try to debug anything :-) directly.

code of conduct - report abuse