3 ms·
To the author of this article: Really great job on it, had great fun reading and also lots of truths in there. But this part: ”Often they have not even bothere
by pietromenna 5y ago
To the author of this article: Really great job on it, had great fun reading and also lots of truths in there. But this part:
”Often they have not even bothered to do basic troubleshooting, things like read the documentation on what the error message is attempting to tell you.”
This happens, but this just means that your Development Team needs some coaching or to improve their quality.
This tells more of a quality of the development team you have been working with. You have to pass along this feedback and ensure that Development team also works with professionalism as everybody else.
DevOps would tell be that "Dev & Ops" would look up issues together (Yes, he will be blocked as well WORKING with you), if you find that it was developer's fault. Tell them: "Hey, this is on your side. You saw how we troubleshooted together. Now each of us has new tricks to use in the future".
If you don't do that, you are the shortest path to get THEIR problem solved. And it is too easy to go that path.
- rswail 5y agoThis is a failure of management, not the "team". They don't need "coaching", this bullshit molly-coddling of people is pathetic. Good management will ensure that if a problem like this occurs, they don't "coach" but they "counsel" the appropriate dev to do their job and not waste everyone else's time.