4 ms·
As a business systems analyst (Product Owner in agile terms) for a fotune 500 company, thank you for this comment. You uplifted my spirits. Also, I agree with
by gxs 13y ago
As a business systems analyst (Product Owner in agile terms) for a fotune 500 company, thank you for this comment. You uplifted my spirits.
Also, I agree with most of it, but I would argue that the best teams I've been on have at least one extremely competent developer, even if not necessarily a great one.
Why? Because I can articulate the product vision and goals working closely with that developer, and together we can make sure the other developers are developing as required.
In an ideal world developers would have all the domain and functional knowledge required to not need people like myself. But the truth of the matter is, that the higher up you go, the more specialized you become, the more you need to do only one or the other.
There are only so many hours in the day - you can either hone your skills as a developer or develop the expertise of keeping multiple business stakeholders happy while holding your own against developers and delivering in a consistent fashion.
- ssmoot 13y agoI'd totally agree with that. I still think your job is more important though and I'd rather work on a team with great management than great developers any day given an either or choice.
- Consultant32452 13y agoIME great developers and great managers are attracted to each other. The few times I've been on great teams (I'm a developer) when the top one or two devs left, the team fell apart. Same thing happened on other teams when the great PM left. The talented people with career mobility know when they're put in a bad spot and have the ability to get out.