MeatballWiki | RecentChanges | Random Page | Indices | Categories

NameTheConflict suggests that often naming a specific pattern, particularly a conflict pattern, helps solve the conflict. However, mentioning a pattern may also make a message seem insincere as it looks mechanical rather than warm and willed. To feel warm and welcoming a message must at least seem not to have any motivation beyond genuine warmth. So mentioning CommunityExpectations right off the bat is okay (as CommunityExpectations are not patterns), but mentioning how we are introducing those CommunityExpectations (a pattern, such as to WelcomeNewcomers) is not always.


Before mentioning a pattern, be sure that the target of your message can AssumeGoodFaith for this message. When the other person is in an AngryCloud (towards you, or the world in general), or you haven't built up any trust yet, there's no use in a message that seems mechanical.


Remember that people on meatball are the good guys, so we're pretty good at assuming GoodFaith. Don't shy away from mentioning patterns if you think they will help. We certainly shouldn't stop talking out of fear of emotional unstability.

Also, this is MeatballWiki where we develop those patterns. If we apply a Pattern without mentioning it and then learn something from doing so, we will write about it on the page in question, and the target will notice and feel even more aggrieved. It's better to be overt about this so you are free to talk about it.


A related AntiPattern is the style particular to Meatball, the PatternFight?.

Contributors: SunirShah, JohannesGijsbers, other(s)


MeatballWiki | RecentChanges | Random Page | Indices | Categories
Edit text of this page | View other revisions | Search MetaWiki