What does that mean?
When I build applications, I like to strictly maintain to all of the perceived standards that I think of or any that might occur to me as I’m building and the variants that I believe are allowable from this consistency.
How about some examples?
Perfect consistency in my folders, components, functions, methods, files, tables, columns, you name it, I’ve got a good reason why I name it or space it or look at it a certain way.
Have you ever looked through a piece of code someone else wrote and changed it to adhere to my precious standards?
You bet.
Have you ever argued relentlessly about such important concepts as how a database table is properly named?
Yes.
Do you ever hold back from imparting your wisdom to your fellow employees by showing them the importance of a file being correctly indented or of a more sane folder structure or a "better way" then they explained?
Daily. More than that if I’m being honest.
Could you go on and on about different aspects of programming that you’ve deem immovable?
No need to answer that one.
What purpose do these standards have other than the noted annoyances caused to others?
I like to think that by strictly maintaining all of these standards, it allows me to use my thought on more important innovation instead of wondering how something is going to be named, or spaced, or whatever.
Where does the practical part come from?
The practical part comes from being, well, practical enough to relent from these relentless standards. For example, I like to name all database table names singularly (item instead of items). What happens when I think a table should be called "group". I have two options. One, when calling the table via SQL, put the table in brackets, so that the reserved word is not taken as such. The other is to break the rule and name this one plural. I choose to name the table plural as I’d rather see an "s" at the end of group, then go through all the SQL code and put brackets around it. Do the brackets even work in all cases? Well, not real sure. Hence, me taking the easy way out and putting an "s" at the of group.
Has anyone ever thought that much about singular or plural table names?
I hope so.
What is the purpose of this rant?
Well, I intended on describing all of the standards as I see them, but then two things happened. One, I fell in love with the Q&A writing style. Two, I don’t think (in most cases) it matters what specific standards you hold. Just that you have standards. You have enough attention to detail to care about something as minute as the naming convention of a file (lower-case first word, upper case first letter of all other words, acronyms should be all CAPS, abbreviations only if you can pick somebody off the street and they’d understand what you mean). You’ve had enough thought about them to be able to stick up for these. But also be practical enough to realize that the other side is better and switch quickly. And, if that you aren’t hurting your productivity too much by sticking to these standards. If you are, then make an exception. Although, you must have a very good reason to stray. In most cases, even if it seems like sticking to standards takes longer, it doesn’t because you need to think less when you look back it at.