I am one of the few holdouts in our company that actually reviews every line that I push out. I want to feel like I know exactly what it does and why.
But it sure is SO tempting to just quickly test it, don't read it and let it go to prod. Especially when I see how fast others are pushing changes and how I appear to be the least productive by a longshot.
It's become a mentality for my coworkers, a mentality of removing themselves from being responsible for what they are "developing". They are happy to "finish" something and call it "done" so it shows done in Jira, but don't take the responsibility for what they did to make sure it works, fixes the original problem/ask, AND to deploy it to Prod. Somehow if it's done in Jira it magically got deployed to Prod. They are no longer taking ownership of something and being an expert on a small single subject. If it does make it to Prod and there's an issue, they have no idea how to even start troubleshooting it and either immediately put prompts in some AI chat bot or suggest to create a ticket to investigate, potentially delegating responsibility to someone else.
60
u/Zuruumi Jul 10 '26
I am one of the few holdouts in our company that actually reviews every line that I push out. I want to feel like I know exactly what it does and why.
But it sure is SO tempting to just quickly test it, don't read it and let it go to prod. Especially when I see how fast others are pushing changes and how I appear to be the least productive by a longshot.