The first rule of Hacker News comments is it's never the engineer's fault

It can be the engineer's fault if it's an engineering mistake. But bad process is the fault of the people who control the process and bad product management is the fault of the people who control the product management.

▲

sfn42 3 days ago | parent [-]

As a developer I work closely with my managers and designers etc to ensure that our project goes smoothly and that we create a good product. I don't necessarily decide what we build but I have a lot of ways to influence what we build and how.

We talk about stuff, we plan stuff, I chip in and people listen. Whenever I see devs complaining about how terrible their project management is I think to myself that the dev is probably at least partially responsible.

Maybe I'm just lucky to have good colleagues, but when I talk about software engineering topics people listen and take it seriously. I think that's a big part of our job as developers, we know the tech and we guide our managers just as they guide us. We're a team, we work together.

▲

lmm 3 days ago | parent [-]

In my experience the kind of project management that doesn't value engineering input on technical matters tends to be exactly the kind of project management that doesn't value engineering input on process changes.

▲

sfn42 a day ago | parent [-]

If I started a new job and it became clear to me that my superiors just wanted me to shut up and do what I'm told, I would be looking for a new job immediately.

	▲	lmm 8 hours ago \| parent [-]
		Sure. But not everyone feels that way, or economic circumstances may be a factor.