Timeline for How should we handle questions that don't have a satisfactory answer but can't be pursued any longer?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2014 at 18:06 | comment | added | ewwhite | Sometimes the professional thing to do is to reformat and reinstall. If there are external factors; deadlines, budget concerns, availability issues... A good engineer knows when to cut their losses and stop the troubleshooting process. The customer often times doesn't care how you arrive at a solution, but rather that it is delivered on-time and on-budget. | |
| Dec 5, 2014 at 21:04 | comment | added | user9517 | No - it's what happened, it's not an answer to the question. | |
| Dec 5, 2014 at 21:03 | comment | added | HopelessN00b Mod | @Iain Well, sometimes it is the answer. I can't even remember how many times I've had to tell the helldesk guys "if you can't fix it in an hour, reimage," so it is an acceptable sysadmin answer/last resort in cases where the troubleshooting and/or fix is just not worth the effort. | |
| Dec 5, 2014 at 21:00 | comment | added | user9517 | Sorry but ' I reinstalled the system' isn't really an acceptable sysadmin answer - home user perhaps | |
| Dec 5, 2014 at 19:38 | history | answered | Ward - Trying CodidactMod | CC BY-SA 3.0 |