1. Cargo cultists, especially when managers.
The typical case involves statements like, "What design pattern are you using?" and "we need to document everywhere we use a design pattern" and the dreaded, "Your code doesn't have enough design patterns".
2. Bikesheds.
The bikeshed problem can lead to ridiculous and endless meetings devoted to the color of icons, or the background shading of icons, etc. I once sat through a meeting in which NINE people dicussed the color of an icon for 30 minutes. Rough labor cost: 1000 dollars [1]. Worse is the fact that bikeshedders think they are contributing, when they are actually wasting money.
3. Titles.
There is a non-trivial chance that your company's "Senior software architect" is a worse programmer than you were at age 18. Not necessarily a problem until he gets it into his head that skills are derived from titles.
[1] Math was wrong on the first run. I calculated the full-length meeting at 3000 dollars. BTW, the icon stayed blue. Light blue.