Timeline for Methods of debugging code (Nightmare situation)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2016 at 18:26 | comment | added | sixtyfootersdude |
The site-specific differences should be managed through Version Control "Branching". - I don't think this is the best way to proceed. Using configuration files and feature toggles seems to be more common and easier to reason about.
|
|
| Jan 16, 2016 at 15:03 | comment | added | gnasher729 | "No documentation about the architecture" usually means "no architecture"... | |
| Jan 16, 2016 at 2:11 | comment | added | Stack Exchange Broke The Law | Runtime errors are caused more by a lack of understanding than a lack of defensive programming. Defensive programming is just a way of hiding the fact that the code doesn't work. | |
| Jan 14, 2016 at 21:58 | comment | added | PerryC | "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live" | |
| Jan 14, 2016 at 12:37 | history | answered | Phill W. | CC BY-SA 3.0 |