> The main idea is to give product teams real problems to solve, and then to give the teams the space to solve them.
First, there's a dearth of high quality engineers in the industry. They've been gobbled up by SV companies with large paychecks and promises of "fuck-you money" paydays. Everyone else gets developers in the range from above average to bad.
Product teams only work with high quality engineers across the entire product. Why? Because if they're shitty, there's no bound to creep of shit code, call it "shit creep" (see footnote 1)
How do you fix a shitty product team, other than replacing the entire team, or product with hopefully a better team?
Sure, feature teams are more limited in scope and their abilities, but they at least constrain the shittyness to a feature. If the feature needs to be replaced, the team can just be replaced, not the entire product.
(1) We've all had to deliver shit code from time to time. The thing is the good engineers know it's shit and refactor it as soon as they can.
You will enjoy your career much more if you quit it with this inverse Lake Woebegone philosophy.
The idea that all engineers outside of a few Silicon Valley companies are mediocre is laughable if you've ever worked at a FAANG. People pick all sorts of jobs for all sorts of reasons.
First, there's a dearth of high quality engineers in the industry. They've been gobbled up by SV companies with large paychecks and promises of "fuck-you money" paydays. Everyone else gets developers in the range from above average to bad.
Product teams only work with high quality engineers across the entire product. Why? Because if they're shitty, there's no bound to creep of shit code, call it "shit creep" (see footnote 1)
How do you fix a shitty product team, other than replacing the entire team, or product with hopefully a better team?
Sure, feature teams are more limited in scope and their abilities, but they at least constrain the shittyness to a feature. If the feature needs to be replaced, the team can just be replaced, not the entire product.
(1) We've all had to deliver shit code from time to time. The thing is the good engineers know it's shit and refactor it as soon as they can.