Timeline for Reopen "How to identify the responsibilities for a health check?" after edit?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Mar 14, 2016 at 19:43 | comment | added | Thomas Owens Mod | @enderland Both "go ask your team" or "go elicit requirements" are non-answers. Any reasonable professional or student software developer should start with these things. People who fall into the target audience for the site should understand this, without needing to ask about it. | |
| Mar 14, 2016 at 19:39 | comment | added | enderland | I... think you are reading way too much into this. The question could just as easily be answered by, "go ask if your team has a protocol/standard/doc for this." In fact, that's a considerably better answer than "go off and generate your own requirements from scratch" (which is the answer your objection here seems to be reacting to ?). When I had a similar question at a new job, I asked our infrastructure team "hey what is the spec for healthchecks?" and they linked me to some documentation. However, I first had to think to do that - it seems the asker of this question hasn't done that yet. | |
| Mar 14, 2016 at 18:51 | history | answered | Thomas OwensMod | CC BY-SA 3.0 |