3 ms·
> STOP CARING ABOUT CODE FORMATTING STYLES Caring about code formatting is not binary. I've seen code that literally breaks syntax highlight in vim, and I've a
by goblin89 12y ago
> STOP CARING ABOUT CODE FORMATTING STYLES
Caring about code formatting is not binary. I've seen code that literally breaks syntax highlight in vim, and I've accepted that sometimes in this job I just have to do syntax-correction commits in order to be able to efficiently work. I'm not a perfectionist about that, but there are limits.
> Every time you make fun of a local company's choices (even if they are badly made), you'll isolate yourself more
I'd say this doesn't only apply to local companies.
Just assume that people you work with are smarter than you.
- JackMorgan 12y agoThere's a big difference to styling your code "when in Rome" like the code around it, and fighting for each team you visit to change their style to match your preferences.
- sophacles 12y agoI like to phrase this as "style doesn't matter, consistent style does". It's important to have consistent style, because once a programmer internalizes the local style - some types of bugs become transparent: the upon understanding what something is supposed to be doing, the style provides visual cues to the flows and a certain predictability in the code. When something is wrong it looks wrong.
- goblin89 12y agoYes, indeed. I think consistency within one file is a good rule of thumb. As an aside, are there any editors that could automagically infer formatting rules (to use for indenting, folding, etc.) upon opening a file? I'm using vim but I think I'd be willing to switch for such a feature.
- goblin89 12y agoNo arguing with that. Just wanted to water down your statement a bit—one can care about formatting style and respect others' choices at the same time. :)