Doing too much work on one's own before looping in others

Re:Doing too much work on one's own before looping in others by closeparen on Tuesday January 25, 2022 @02:33PM (#30076820)

I think it's management and their "agile" philosophy that's toxic here, intentionally depriving engineers of any sense of ownership, autonomy, or vision-fulfillment over their work by constantly bouncing them around across small disjoint tasks.

I am incredibly fortunate to work in a place that values ownership, both explicitly and in practice. Given how widespread the opposing value system is, I'm afraid to ever leave.

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by someguydave on Tuesday January 25, 2022 @08:25PM (#30080488)

because programmers must be replaceable parts for the industry to keep going at status quo

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by closeparen on Tuesday January 25, 2022 @08:41PM (#30080589)

We have plenty of turnover and it works out fine. In fact turnover of the senior engineers who are service/project owners usually creates the opening for one of the more junior contributors to demonstrate L+1 competency by taking over.

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by someguydave on Thursday January 27, 2022 @08:02AM (#30100008)

“the status quo is fine”

[ Parent | on HN ]

Re:Doing too much work on one's own before looping in others by closeparen on Thursday January 27, 2022 @02:30PM (#30105099)

Of course the status quo is fine, you're one of the highest paid people in one of the cushiest occupations in all of human history.

[ Parent | on HN ]