3 ms·
This seems to be a pretty common setup. I’ve heard opinions on both sides about whether it is a good idea. One of the biggest challenges with it for me is tha
by MattGaiser 5y ago
This seems to be a pretty common setup. I’ve heard opinions on both sides about whether it is a good idea.
One of the biggest challenges with it for me is that a dev who is a dev is a very different personality who a dev who manages the entire SDLC.
The former placed in the latter environment is going to be lost and annoyed at all the moving parts. They signed up to write code and to trust that the process would deliver good requirements.
The latter in the former environment is going to be frustrated by all the process. They signed up to really own the product and realize that they really just own a block of a process.
I suspect either can work if you have people suited for each. Switching people between them sounds like a recipe for attrition though.
- UglyToad 5y agoA term I've seen floating around for the latter is a product engineer/developer. This makes the distinction between people who view their jobs as coding to meet requirements vs. solving business problems just happening to use code.
- MattGaiser 5y agoYep. I actually interviewed for a job like that and that was the title.