Loosely related thoughts: If I feel like it, I can tell my editor to display `underscore_functions` as `underscoreFunctions` without actually modifying the tex

Loosely related thoughts: If I feel like it, I can tell my editor to display `underscore_functions` as `underscoreFunctions` without actually modifying the text. I don't feel like it. Here's my official "coding standards": Whitespace standards (as in "only spaces" or "only tabs" for indentation) are good. Use whatever's already there. Your VC system can probably handle it for you. I consider standards for things that don't add ridiculous diff noise as "soft". I'd rather run a tool like sonar that can generate "hey, this is ugly crap" reports with blame annotations than reject commits for style violations. I'd consider rejecting commits for really nasty style violations that weren't covered by tests. I'd also consider making people wear a monocle if they're going to be doing a bunch of "just style" edits. But meh. On the other hand, a consistent codebase is a nice thing. If it's a large codebase, a very nice thing ... but it's more of icing on the cake than the cake itself. I don't want to eat a whole bowl of icing.