DEV Community

Discussion on: Let me do my damn job or do it yourself

Collapse
thinkslynk profile image
Stephen Dycus

I think he's referring to the fact that an issue so visually obvious should have been caught before being pushed live. I've definitely worked with an annoying owner finding bugs at 3am, but if something so obvious can make it to production, then perhaps your release pipeline is broken. If you have a proper staging environment that matches production and you always push to staging first, this should have been caught before going live. I get that we work in an era where QA jobs just don't exist because companies think devs are trained to provide proper QA, but this issue could have been noticed by just clicking through each page.

Not a judgment by the way. I've worked in environments in which the release cycle is so quick that it's often easier to just push it live and fix it later, and the owners want you to somehow fix the bugs that are pilling up but without giving you extra time to do them. But if the owner gives you shit, counter by asking for time to design and implement a proper release pipeline. If he doesn't give it to you, then you remind him every time he catches a bug "A proper release pipeline would have caught this early."

Thread Thread
spirodonfl profile image
Spiro Floropoulos Author

The premise here is that the owner actually listens to you, even once, let alone on a repetitive basis. That's not the case.

Thanks for the comment.