Comment by halJordan
7 days ago
I think it's past time we stop letting the doers of an org pass off responsibility for their actions. The engineers coded this. It is on them as much as it's on some nameless exec
7 days ago
I think it's past time we stop letting the doers of an org pass off responsibility for their actions. The engineers coded this. It is on them as much as it's on some nameless exec
I don't agree. There's a limit on how much you can influence things, and as a dev (or product owner or whatever) you need to pick your battles.
How a decision is made, what gets released etc. are all opaque processes and blaming the devs from the outside is not productive.
That said, I'm all for it for devs becoming more responsible for the end result, evaluated within the org boundaries. Especially these days when people tend to cop out with "oh cloude did it / didn't catch it" responses (before, it was "oh I had to come up with something quick and couldn't check everything").
It is usually an exec with a name, just like engineers have name.
Quality is achieved by process - testing, coherent requirements etc. Individual engineer cant change those.
Unless they're founding engineers, engineers are exployed to work on what a company wants. If the company wants to cut corners in exchange for something else, their only usual options are cutting corners indeed, or quitting.