Timeline for What to do about manager who does not want to give detailed requirements?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2018 at 22:08 | comment | added | Simon B | As a team, own the code. If the boss wants bugs fixed, it's up to you to work out how to fix them, what reversion testing is required, how to configure the code, and so on. | |
| Mar 21, 2018 at 19:31 | comment | added | Sh4d0wsPlyr | Love the quote - and I expect something similar to this is where I will end up going. The issue is that I might not understand the business or requirements I am programming for until after. An example is when the requirement is given I clarify and do it properly, however may not realize other sections of the software are also going to need to be impacted (think side effects that are business specific, but I do not know the business rules, only my boss knows them). | |
| Mar 21, 2018 at 16:17 | history | edited | Chris E | CC BY-SA 3.0 |
Emphasized that most excellent saying so it's more obvious.
|
| Mar 21, 2018 at 15:21 | history | answered | Daniel | CC BY-SA 3.0 |