| Do product manager actually treat software engineers as humans though? It works both ways. How do you know the OP is toxic? Is it because they are jaded by the amount of times they have told product / architect on the actual implications but have been ignored? We've lost how things should work. Is all that matters the design, the idea of a feature or the architecture diagram and ignore everything in practice? Everything sounds good in theory. I've seen way too many product owners add features without understanding the implications and no 1 from engineer has the power to stop it. When it blows up the engineers get blamed even if they've made enough noise. If you were building a house, it'd crash and lives would die. Real architects are way more responsible. Why don't you think about why we've come to this state? There are multiple comments agreeing with the OP and we've all experienced it. The manager considers engineering as a "resource" and whether we're backend, frontend or whatever we're all the same and can do the same work. If there's a crunch just throw more "resources" at it, right? No! It doesn't work like that. |