3 ms·
> You have to interface between business and stakeholder requirements, modeling the domain effectively, engineering management, product processes and then reali
by Geminidog 6y ago
> You have to interface between business and stakeholder requirements, modeling the domain effectively, engineering management, product processes and then reality
This is the Technical product managers job. The architects role is suppose to be an extreme high level view of purely the technical side of the business.
From my own anecdotal experience "architects" who try to fulfill the role to the definition end up being mostly useless.
- pc86 6y agoI'm biased, as an architect, but you can't be a good software architect if you don't know the domain very well - both the industry as a whole, and your company specifically.
- nitrogen 6y agoI've had my worst experiences in teams where the Product and Engineering were completely siloed. Things go a lot more smoothly if there's a bit of overlap. Also, many orgs don't have a TPM role, so that falls on Staff/Principal engineers and engineering managers. In fact, roles should be fluid and slightly overlapping, as every team and every org will have different needs.