Any more I just use the intellj idea defaults. More on reddit.com

Is there a good extension or proven methodology to automatically format Java code in VSCode to adhere to Google's Java Styleguide? Nothing from the list of links below seems to work for my set-up. ... More on stackoverflow.com

In the latest versions of IntelliJ IDEA it seems that it isn't possible to import code style files like intellij-java-google-style.xml. I would like use the Google Java Code Style in this IDE but it More on stackoverflow.com

In typical Goolag fashion, it's very grand, but unfortunately it's also largely pointless because very few people can keep all these rules in their head for very long. Most of their rules don't really matter, and seem to be there to convince the reader that the author of the style guide is very learned in the subject of writing. As noted by another comment in this discussion, the most important thing about writing documentation is that it actually gets done in the first place. Accuracy is the second most important thing about writing documentation. Finally, we get to consistency. If a person/programmer/writer is actually serious about making their documentation consistent, then it is incredibly important to write as much of it at the same time as possible. This is absolutely the easiest way to make it all nice and consistent. If you write as much as possible at the same time, you're much more likely to use all the same phrases and nomenclature because they'll be active in your brain. If you write chunks of docs a few weeks apart, then you'll use whatever language is in your brain when you're writing, and the results will be far less consistent. Finally, if you're documenting code "class by class" then it's really hard to see how you documented something similar. You have to keep multiple files open, and hunt and peck through them. For this reason, it's REALLY wonderful if you can write the documentation in a single document so that you can see the other documentation nearby. Sources: Have documented enormous APIs. We had huge consistency improvements when a system was documented all at once rather than one piece at a time. We also had enormous improvements in speed and consistency when the documentation could be written in a single document rather than having to document all the classes in separate documents ( like in the headers above parameter lists ). EDITED TO ADD: class A { int count; float bias; void SetCount( const int count ); int GetCount() const; void SetBias( const float bias ); float GetBias() const; } If you have a large number of classes, a lot of context switching is required to write documentation. By context-switching, I mean opening other classes and figuring stuff out. That's why it's easier if you have a single document that has the following info. ( This document is created by a machine, and filled in a by a human. ) CLASS, A, MEMBER, int, count, MEMBER, float, bias, MEMBER, void, SetCount, PARAM, const int count, MEMBER, int, GetCount, MEMBER, void, SetBias, PARAM, const float bias, MEMBER, float, GetBias, CLASS, B, ... This makes it easy to see large amounts of the documentation at the same time, which makes it easy to ensure that things are done consistently. It also gives the developer/author a finish line since they can see what's undocumented and know how much more they have to do. It's also INCREDIBLY fast because you don't have to hunt for files, open files, and do searches all the time. More on reddit.com