Suggestions: Anti-Pattern counter-examples
It seems like this exact question hasn't been asked before, so I skip:
Most of us are familiar with the concept of anti-pattern. However, avoiding anti-pattern implementation can in principle swing too far and cause problems. For example, the Design by Committee has a counterexample, which I would call Design by Maverick - in which the design of an important function is delegated to an individual to do what they think is best, with the goal of reviewing their work later and deciding whether whether it should be finalized or go through another iteration. In practice, this takes much longer as the rest of the team is busy with other things and might be useful to some, especially if Maverick is not the experienced end user himself.
Does anyone else have examples of anti-boilerplate counter examples?
a source to share
I see the problem in the anti-templates themselves. It's easy to point out the wrong solutions, but it's harder to come up with good ones. Almost always the quality of a solution depends on the context, so sometimes even an anti-pattern can be used more in its implementation than other solutions. So the space for solutions or patterns in general is pretty inexhaustible and we have to decide which ones to look at. Bad decisions or good fixes? I think that looking at bad solutions and knowing that they are bad is not as useful as looking at good ones, because from good (common patterns) you can also get good principles that were used in solving this solution (as is the case with OO Design Principles in GoF Design Models Book). As for your exact example, I heard somewhere about "benevolent dictator"and some kind of democracy (with its own name), which was adjusted by adding more votes for certain people depending on the different priorities of the project.
a source to share