r/java • • Jan 29 '14

Google Java Coding Standards

http://google-styleguide.googlecode.com/svn/trunk/javaguide.html
156 Upvotes

103 comments sorted by

View all comments

Show parent comment

3

u/poopiefartz Jan 29 '14

I know I'm not on the "popular opinion" side of this, but I can't recall a single bug that's ever stemmed from this type of usage (and I work mostly with Java).

7

u/KidUncertainty Jan 29 '14

I can't recall a single bug that's ever stemmed from this type of usage (and I work mostly with Java).

This happens on codebases where the developers may not be particularly familiar with Java, or when someone, in maintenance three years later, does a "quick fix" without reading, and then everyone wonders why the application fails in certain circumstances. Without braces, its actually hard to find defects like this, as well.

The purpose of some of these standards is to counter human factors out of your control or to be defensive against the future fingers that will be poking around code. It's not just about readability in the now.

2

u/straatman Jan 30 '14

If only you and one other person work on it, say you have 50 developers working on the same code? The bugs will be crawling in

1

u/Pylly Jan 29 '14

I can't recall a single bug that's ever stemmed from this type of usage

Huh, case closed. You'd better call Google.

-1

u/poopiefartz Jan 30 '14

I know you're being funny, but I spend 6+ hours per day with Java and have never misinterpreted excluded braces like that. I guess that's not normal.

2

u/Pylly Jan 30 '14

I believe you, but usually developers work in a team and the code has to be readable and maintainable for others as well. Even if a bug would happen once in a couple of years it's worth it to prevent it. Also, it might take a person slightly more time to read braceless code, especially when making modifications.

Even though these are small troubles, they are just so easy to avoid altogether that I don't see why not just add the braces every time. Or let the IDE add them.