News for hackers. Stuff that matters.
Re:The Framing of the Developer by 29athrowaway on Wednesday May 06, 2020 @10:57AM (#23091671)
For every position, there is a chance of a bad hire. PMs are no exception. Every productive employee has a chance of losing motivation and start underperforming. Again, PMs are no exception.

You organization needs ways to detect and "fix" situations caused by a person not living up to their role.

Balance of power between product and engineering is one of such circuit breakers.

Re:The Framing of the Developer by AmericanChopper on Wednesday May 06, 2020 @02:32PM (#23094631)
A balance of power between engineering and product ownership is a terrible idea. The role of engineer doesn’t necessarily require any understanding of the customers needs. If you have an engineering team that understands them well, it’s either because of competent product ownership, or it’s a complete coincidence. Engineering should not have control over what is built, or have the power to override product owner’s decisions. Product owners should not have control over how things are built, or the ability to override engineering leadership’s decisions. They’re simply different areas of responsibility, there is no need at all for a balance in power between the two, and creating one for the purpose of avoiding bad decisions is just as likely to be used for avoiding good decisions, or decisions that conflict with somebody’s personal taste or political objectives.
Re:The Framing of the Developer by 29athrowaway on Thursday May 07, 2020 @12:31AM (#23099743)
Deciding what to build, and for how long, indirectly dictates you how things are built.

Deciding which engineers should have a career advancement also influences how the product is built.

Re:The Framing of the Developer by AmericanChopper on Thursday May 07, 2020 @07:17AM (#23101734)
It sounds like you’re describing your own experience of office politics more than anything relating to the roles of product and technical leadership.