When you try to explain the new coding convetions to your colleagues

Got a task named: "Final Changes", made a wünderlist named: "Final Changes v1" just because if PMs thought me something is that the words coming from their mouth and the ones in dictionary have a completely different meaning..

Sometimes my hatred for code is so.. overwhelming that I think I need a sabbatical or should even stop altogether.

Let's face it. All code sucks. Just on different levels.
Want to go all bare metal? Love low level bit fiddling. Well, have fun searching for concurrency, memory corruption bugs. Still feel confident? Get ulcers from large C/C++ code base already in production, where something in the shared memory, function pointer magic is not totally right?
So you strive for more clean abstractions, fancy the high level stuff? Well, can you make sense of gcc's template error messages, are you ready for the monad, leaving behind the mundane everyday programmers, who still wonders about the scope of x and xs?

Wherever you go. Isn't it a stinking shit pile of entropy, arbitrary human made conventions? You're just getting more familiar with them, so you don't question them, they become your second skin, you become proficient - congrats you're a member of the 1337.

Does anyone work with EditorConfig files in VS?

dotnet_naming_rule.Variable_bool.symbols = Variable_bool
dotnet_naming_symbols.Variable_bool.applicable_kinds = field
dotnet_naming_style.Variable_bool.required_prefix = b
dotnet_naming_style.Variable_bool.capitalization = camel_case
dotnet_naming_rule.Variable_bool.severity = suggestion

this is part of one i'm currently working on. My intention is to let it detect every boolean variable that is not named correctly. Am i doing this right? Am I missing something? (Because at the moment it doesn't work).