If I were a minority or worse at getting along with others I'd definitely avoid flat management schemes as well.
> Agreed
Unless you have a team of unusually conscientious engineers, "democratic" or "flat" decision-making often translates to who shouts the loudest.
> Not to mention engineers often want to complete the project in the most technically exciting way possible, rather than the way that will most benefit the product.
Also sadly true and even has a name: Resume Driven Development
> Flat structure + too many engineers like that and you end up with this http://www.smbc-comics.com/?id=2597, written in Haskell.
Aww, why pick on Haskell here? You know Bump[0] used Haskell. Point being that Haskell can be a choice which is a choice that most benefits the product. I recently had experience writing an app to deal with medical data sets that really benefited from correct by construction or wholemeal[1] programming.
0: https://www.fpcomplete.com/wp-content/uploads/Bump-case-stud... 1: http://stackoverflow.com/questions/6957270/what-is-wholemeal...
Noted as a good example in the stack overflow answer:
> I always found the Hutton/Bird Sudoku solver a good example of wholemeal programming: http://www.cs.nott.ac.uk/~gmh/sudoku.lhs
Or the one that has the most political capital.
Well, this has a habit of happening everywhere, no matter who is running the show.
Unless you have a team of unusually conscientious engineers, "democratic" or "flat" decision-making often translates to who shouts the loudest.
Not to mention engineers often want to complete the project in the most technically exciting way possible, rather than the way that will most benefit the product. Flat structure + too many engineers like that and you end up with this http://www.smbc-comics.com/?id=2597, written in Haskell.