One thing I always appreciated was “beautiful” code. The product may not be great but, wow, that code is beautiful! I will admit, if it wasn’t for the way editors are set up these days I would probably not write beautiful code, it would be legible and easy to follow because I do have my own “built in” style for programming for 30+ years and it’s not too bad.
However, when you work on larger projects, with many contributors, especially open source projects… this is where coding styles is definitely needed.
There is nothing worse than flipping between files in a single project to see the source code completely different from file to file. The solution is to make all developers use the same editor with the style enabled or publish your coding style so everyone can easily follow it. The editor idea is the best, because then the editor just formats the code as you go. In some editors you can even setup style warnings.
Take a look at the differences:
Neither one is right or wrong, the important thing is to be consistent throughout the project. Like I said earlier, the best thing to do is to setup your editor to do most of this for you.