4 ms·
and we get yelled at when we can't deliver a feature because some gatekeeper is sitting atop his little throne in the kingdom of servers saying no. ;) This is
by serge2k 10y ago
and we get yelled at when we can't deliver a feature because some gatekeeper is sitting atop his little throne in the kingdom of servers saying no. ;)
This is institutional failure.
- jstimpfle 10y agoExample?
- user5994461 10y agoHonestly. Developers should stop thinking that their jobs is to release features all the time at all costs. That's simply not true and that's counter productive for the business.
- WorldMaker 10y agoIf only the business might learn that it's not their jobs to request new features all the time at all costs... If only customers weren't fickle and might learn not to demand new features all the time whatever the costs... It's turtles all the way down.
- user5994461 10y agoAnd in the end, that's the developer who always gets the decision. Does he ships half assed half finished every single time, or does he take time to do some testing and not break production.
- serge2k 10y agoDevelopers do what the business wants them to.
- CaptSpify 10y agoThen place the blame on the gatekeeper. As a sysadmin, I'd be more than happy with you pointing the finger at me as the reason why you can't deliver a feature. Assuming, of course, that you've run the proper tests and gotten QA's approval.