4 ms·
Take my comment with a grain of salt because I have never worked for Amazon and I don't have any relationship with the company. Since these are Amazon employee
by mkl95 3y ago
Take my comment with a grain of salt because I have never worked for Amazon and I don't have any relationship with the company.
Since these are Amazon employees, I would expect them to experience the downsides of being a consultant, such as alienation, and the downsides of belonging to a product organization, such as extreme pressure.
> As organizations grow, engineers’ code intertwines with other engineers’ work, making it difficult for teams to complete their features independently.
The current consensus in the industry is that it should be the opposite. To grow in a healthy way, teams should be as decoupled as possible.
> The away team model is a powerful and flexible mechanism for removing dependencies between teams. However, it should not be the first option for developing necessary changes to a system dependency.
Did I miss something? You introduced this team model because there was a dependency, but you never removed it. This post is full of contradictions.
- jq-r 3y ago> Did I miss something? You introduced this team model because there was a dependency, but you never removed it. This post is full of contradictions. It's just another article by a manager expounding the virtues of a managerial fad to score points in his org. Sounds great to his peers, sounds like a nightmare to ICs.
- dbish 3y agoNot even a manager, his LI says solutions architect which is neither an engineer or manager so he would not have first hand experience doing it for actual software dev.
- jq-r 3y agoRight, those "solutions architects" like "Techical Account Managers" which act like moats against receiving any kind of good support. Those guys are just terrible IMO unfortunately.