Things We Always Remind Ourselves While Coding

Re:Things We Always Remind Ourselves While Coding by CM30 on Saturday November 25, 2023 @08:15AM (#38413285)

Not in my experience. For one thing, this is usually what the peer review process, tests and QA team are there to fix. Almost everyone's work will have at least some things that need improvement/fixing before they can go live, but there's a process to make sure they don't go through into production without those fixes.

If the issue actually happens in production and say, a bank's payment API goes down that may be a different story, but even then I've usually seen the managers say it was a process issue rather than finding someone responsible and calling for their firing. Or as the old story goes, treating it like an expensive learning experience.

But eh, your mileage may vary.

[ Parent | on HN ]

Re:Things We Always Remind Ourselves While Coding by ulizzle on Saturday November 25, 2023 @11:09AM (#38414366)

I suppose you do have a monopoly on the truth.

[ Parent | on HN ]

Re:Things We Always Remind Ourselves While Coding by windmark on Sunday November 26, 2023 @05:09AM (#38420502)

We got your point the first time you posted this. You come across as someone who tries to keep the monopoly for themselves.

[ Parent | on HN ]

Re:Things We Always Remind Ourselves While Coding by salawat on Sunday November 26, 2023 @01:36PM (#38423808)

>For one thing, this is usually what the peer review process, tests and QA team are there to fix.

The QA team are not your personal team of muckrakers. The more you treat them as such, the faster we burn out, because it's our job to say no, and saying no is a recipe for interpersonal disaster or attrition in an org, especially once management inevitably starts overriding the department consistently, regardless of the amount of risk that they end up taking on in spite of it.

[ Parent | on HN ]