Timeline for Methods of debugging code (Nightmare situation)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2016 at 4:24 | comment | added | candied_orange | "Your intentions are good, but this is not something we should be focusing on". Of everything you've mentioned this is the most toxic. Someone else must be new enough to also think this is crazy. Get together and start a quiet revolution of competent development. Use source control together. Add tests and logging. But get your assigned work done. If you get caught and questioned about it just shrug and say this is what professionals do now. You can run but I can tell you. Anyplace that has been developing over a year is doing something outdated and probably something stupid too. | |
| Jan 15, 2016 at 23:09 | comment | added | Martin Schröder | @Igneous01: Run, don't walk. This place is sick and will make you sick. | |
| Jan 14, 2016 at 13:10 | comment | added | Mawg | Yup, start logging & tracing. Also start documenting, and adding comments. Bit by bit, it will all add up. Also, you say that you are lucky enough to still have some of the original coders in the company, if not the team. Push management to get accecss to them If possible, persuade them that they would rather produce some docs than be constantly approached with questions. | |
| Jan 14, 2016 at 7:03 | history | edited | user53141 | CC BY-SA 3.0 | added 7 characters in body |
| Jan 14, 2016 at 6:59 | comment | added | user53141 | And keep in mind that when bad policies fail, everyone involved looks bad, even those who disagreed. | |
| Jan 14, 2016 at 6:54 | comment | added | cmaster - reinstate monica | @Igneous01 Honestly, try to find a different mountain to climb. Work conditions at other places may not be perfect, but I guess at least most are significantly better than what you are experiencing. If your gatekeepers reject your improvements with "this is not something we should be focusing on", it's their decision to make, and they will reap the results of that failed policy (they are already loosing tons of money in terms of lost development time). The question is, do you want to stick with them until they do? | |
| Jan 14, 2016 at 4:26 | comment | added | Igneous01 | Believe me, I would want nothing more than to add asserts, guards, and logging, probably rewrite the data layer as well (I'm writing a configuration validator to diagnose typical configuration issues). Unfortunately it's not up to me. I can make a request to have something pushed into source safe, but the typical response is 'your intentions are good, but this is not something we should be focusing on'. Alas, I am but a junior with 1/2 years experience. I'll be climbing this mountain for a while. | |
| Jan 14, 2016 at 4:06 | history | answered | user53141 | CC BY-SA 3.0 |