I've learned from working in one of the largest companies that there are two kinds of development teams:
(1) the teams that mostly depend on the products of other teams;
(2) the teams that create products that others depend on.
And when the upper management starts rushing the deadlines sacrificing quality for the deliverables guess which team becomes (A) and which team becomes (B)?
I currently work in a (B) team, and I try as hard as I can to "move fast and break things" but there is simply no way of doing that because every significant code change that I make requires changing the code we don't own. Since the code that we don't own is written in such scrappy way that you better don't touch it or else it breaks, our team has to resort to only minor insignificant code changes.
>>As an engineer, I've learned that it's less work and more rewarding to be on the (A) teams than on the (B) teams.
It is certainly more rewarding to be on the (A) team, but do we always have a choice?
>>As an engineer, I've learned that it's less work and more rewarding to be on the (A) teams than on the (B) teams. It is certainly more rewarding to be on the (A) team, but do we always have a choice?