News for hackers. Stuff that matters.
Re:How should I behave as a developer in a project that's he... by loup-vaillant on Wednesday May 29, 2013 @05:51PM (#5789400)
> It's very frequent that "Team A" works on a software product and gets some of it done. Then the work gets sent to "Team B".

First: why is that? Are there good reasons for this, and does this happen for those reasons?

Now, knowing nothing about the company, if I learn that every other project suffer a change of team before going into maintenance (officially and actually), then it's substantial evidence that something is wrong with management.

Whether one should quit of course depends on how wrong.

There are no comments on this comment yet.