Completely agree that reformat beats style checking. I think reformat also subsumes style checking from a code complexity perspective, so consider this a step on that path. Launch and iterate.
As for the rest of your comment: we've been using this thing for 9 months. It has made us more productive. It's made it easier to onboard new people in to the code base. It doesn't cost much - you pretty quickly stop seeing errors as you get used to the conventions. By letting a script worry about these admittedly less important details we have MORE time to talk about exceptions, libraries, locking, etc.
So, while in theory much of your comment sounds true, I can state very conclusively that in practice it hasn't happened the way you suggest.
(Also, naming conventions and documentation are important things enforced by the script. Maybe you didn't see part? I'll make it clearer in the README.)
As for the rest of your comment: we've been using this thing for 9 months. It has made us more productive. It's made it easier to onboard new people in to the code base. It doesn't cost much - you pretty quickly stop seeing errors as you get used to the conventions. By letting a script worry about these admittedly less important details we have MORE time to talk about exceptions, libraries, locking, etc.
So, while in theory much of your comment sounds true, I can state very conclusively that in practice it hasn't happened the way you suggest.
(Also, naming conventions and documentation are important things enforced by the script. Maybe you didn't see part? I'll make it clearer in the README.)