Simplified and removed unnecessary rules. #5
Conversation
| These are conventions that we've come to through consensus on our own team. We all individually have slightly different styles, but we determined that things would go a lot smoother, and code would read a lot more consistently (and cause fewer nervous tics) if we came to some compromises on how we write code. We don't stubbornly stick to our guns, even though nobody's forcing us to change. Good programmers don't need bosses to work harmoniously. We would love to use software to do this for us, but the existing stuff out there (like Uncrustify) isn't currently flexible enough to do what we want. We're interested in rolling our own or modifying something existing, but that takes time too. We'd be happy to collaborate on such a tool, though! Let us know if you start something up. :) |
README.md Outdated
There was a problem hiding this comment.
This change clearly requires a newfile at file's end. It is the One True Way as any one with Common Sense knows.
| Hmm… I feel a better replacement would be something like this: http://xkcd.com/386/ |
4 participants
There is a tendency when writing coding conventions to treat programmers as computers who, if given exactly the right instructions, will produce the desired output. So authors lump in more and more rules, in the quest for absolute consistency.
Unfortunately (for coding convention authors) programmers are not machines, and will not do what you tell them to. They will keep doing what they've always done, unless their boss forces them to follow the rules.
And if they are forced to, what then? Instead of worrying about the code they're writing, the programmers must worry about whether they have fulfilled the ever evolving set of coding conventions.
Any good programmer, the kind that I'm sure GitHub employs, will alter the styling of the code they write to match what's already there. And - as human beings - they will not perform this task 100% perfectly. Nor should they try to.
If you actually need absolute consistency in how your code is styled, instead of wasting the time of highly paid people, why not write a computer program to do it?