1) break & meeting
"Break" can be said to be the number one killer of programmer productivity, because after being interrupted difficult to return to the place before, need to sort out ideas, probably half an hour later.
The more times interrupted, the stronger the frustration, productivity is low, the more bug, a series of vicious reaction.
If it was interrupted in the morning, then this day is probably not what the job.
Meet it? The meeting is "a planned break."
2) trivial type management
Such managers are a stumbling block to the development team, he likes a little broken thing to a meeting, you have a problem go harassment.
Not only that, his lack of confidence in the team, and you always like to pull the details.
Programmers deal with such managers got in trouble, will often be interrupted, so programmers turnover rate of these teams is very high.
3) ambiguous
For example, receive a bug "this feature does not help, quickly changing for the better!", I believe who see such a vague description would look ignorant.
Such as product requirements document a clear description of the function, you develop according to their own understanding, then product manager came up and said you do not develop, so ...... should rely on! We had to re-develop.
For example, you're struggling to knock the code, quietly, the manager came to your side, telling you to do a xxx function, then left, whether you do not understand the reason, do not tell you this priority task, like a gust of wind.
4) Seagull Management
In case you have not encountered this type of leadership: usually no matter what, but will occasionally pop out to find fault with fault-finding, "You did it wrong", "You do sucks" ......
Like a seagull, washed down occasionally to confuse things.
5) to get credit
Many teams will have this kind of villain, he will express themselves especially in leadership there, you did two weeks of the results said to his credit.
This one makes the team very chilling.
6) demand peristalsis
for example:
Version 1 (prior to implementation): This function is to "show map this location."
Version 2 (to be developed in version 1 when done): Function to "show the position of the 3D map."
Version 3 (Version 2 almost in development, when finished): functionality changed to "display a 3D map of the location, and the user can fly past."
XX of you, without so grueling.
7) compression hours
Some managers seem very democratic:
"The features you need to develop How long?"
"3 days of it."
"Project time is very tight, hard-point half days to finish it."
"Really get it working half days."
"That's two days now."
"Ok"
He succeeded lower prices, but also that he respects your idea, your own scheduled completion time.
summary
这几个问题都是非常普遍的，你遇到过哪些？欢迎吐槽。
推荐阅读：
