The whole point is to dumb a problem down so that people can focus on substance instead of form. It’s typesetting for people who aren’t technical and to lower the barrier for technical people for documentation of what they’re working on so far that you can ridicule people who still refuse to document their shit.
Any time you can make a developer chose between belligerence or stupidity to explain their behavior, they will either change the behavior or go with belligerence because they’d rather be dead than thought stupid. In either case you have maneuvered them out of being able to continue to be obstructive to team dynamics.
So you “solve” social problems with technical solutions not by making the solution better, but by making it the dumbest thing ever so only an idiot wouldn’t understand it.
It’s called markdown because it contains simple markup. Some of that is structural, no argument, but it’s also layout. Just enough to keep readers on board with what you’re saying.
Any time you can make a developer chose between belligerence or stupidity to explain their behavior, they will either change the behavior or go with belligerence because they’d rather be dead than thought stupid. In either case you have maneuvered them out of being able to continue to be obstructive to team dynamics.
So you “solve” social problems with technical solutions not by making the solution better, but by making it the dumbest thing ever so only an idiot wouldn’t understand it.