Timeline for Methods of debugging code (Nightmare situation)
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2016 at 10:08 | answer | added | 20c | timeline score: 0 | |
| Jan 24, 2016 at 11:32 | history | tweeted | twitter.com/StackProgrammer/status/691222019963277312 | ||
| Jan 16, 2016 at 15:56 | answer | added | JacquesB | timeline score: 0 | |
| Jan 16, 2016 at 8:40 | comment | added | kevin cline | how I manage these situations: if I'm not being paid well above market, I go find something else to do. | |
| S Jan 15, 2016 at 23:16 | history | suggested | Martin Schröder | CC BY-SA 3.0 | fix markup |
| Jan 15, 2016 at 23:06 | review | Suggested edits | |||
| S Jan 15, 2016 at 23:16 | |||||
| Jan 15, 2016 at 6:18 | answer | added | radarbob | timeline score: 4 | |
| Jan 14, 2016 at 21:53 | answer | added | Jon Raynor | timeline score: 5 | |
| Jan 14, 2016 at 12:37 | answer | added | Phill W. | timeline score: 8 | |
| Jan 14, 2016 at 7:30 | review | Close votes | |||
| Jan 24, 2016 at 3:07 | |||||
| Jan 14, 2016 at 6:58 | comment | added | user53141 | Here is some actual career advice: Spend too long in a house that has horrible software engineering practices and you will likely be blamed by management for being a bad developer for the issues that inevitably ensue. I've been there, and I am sure others have as well. At the very, very best, it leads to bad development habits. | |
| Jan 14, 2016 at 5:45 | comment | added | Igneous01 | I was not being completely honest with requirement 1. It is possible to use debugger, but only for 'core' code that does not vary from client to client. But in the front end/datalayer, certain logic won't fire if it doesn't detect that client. The custom binaries (that are not debuggable) change the behaviour of the database, datalayer, and front end. | |
| Jan 14, 2016 at 5:40 | history | edited | Igneous01 | CC BY-SA 3.0 | added 400 characters in body |
| Jan 14, 2016 at 5:31 | comment | added | user4828 | Given requirement #1 the only way to be effective at debugging this mess is to be clairvoyant. Seriously, there is no magic bullet that is going to make this anything but a crapshoot. In some ways this should take some pressure off of you, since debugging is necessarily a matter of luck. Or is your management going to order you to be lucky? Clearly this isn't sustainable, so you should be looking for other opportunities. | |
| Jan 14, 2016 at 5:08 | comment | added | BrianH | +1 for "I want to shoot myself as well". Source Safe 2005, ouch. Well, at least you should 'focus' on the wonderful history lesson - you are basically a time-traveler! You'll learn the lessons of a decade of carefully developed knowledge of "so this is why we don't do that anymore". Godspeed, grasshopper. | |
| Jan 14, 2016 at 4:06 | answer | added | user53141 | timeline score: 22 | |
| Jan 14, 2016 at 3:06 | comment | added | Robert Harvey | Do you have a résumé? | |
| Jan 14, 2016 at 2:59 | history | asked | Igneous01 | CC BY-SA 3.0 |