3 ms·
The problem often lies with the entire Organization and not the Development team. I've had roles where Development was empowered to code the product and deploy
by lucasyvas 5y ago
The problem often lies with the entire Organization and not the Development team. I've had roles where Development was empowered to code the product and deploy the code, which necessitates certain access. At that point, troubleshooting is trivial and we can solve our own problems. It's amazing.
Throw in some red tape where I can't have access to logs myself? Then I don't care to fix it at all - chasing another team, that has diverging priorities, is complete a waste of my time.
If your Developers are tossing shit over a wall, I'd bet top dollar you work in organization B. In which case they are behaving accordingly. Don't empower me to identify and fix issues? Then I won't (and I won't lose sleep over it either).
- goodells 5y agoI've been in both kinds of organizations. Without fail, every place that was like "organization B" (separate development and cloud teams) had some under-the-table workaround. The worst I think I ever saw was _every single customer's hosted environment_ had SSH access enabled with the same key, and it was shared between developers without much regard for security. A business worth hundreds of millions of dollars... But of course they required two-factor authentication in O365, so it was SOX2 compliant.