3 ms·
Sometimes I arrange my variable declarations so that they make a picture of something in profile... ... don't hate me because I'm beautiful ... :D ---- On a
by Stormbringer 16y ago
Sometimes I arrange my variable declarations so that they make a picture of something in profile...
... don't hate me because I'm beautiful ... :D
----
On a more serious note, something I have noticed working on large projects with other programmers, is that if each programmer has their own distinctive style and conventions, then you can tell straight away by looking at it who wrote it, and more importantly who modified it.
Thus if Billy (who is an idiot) modified something written by Sheila (who is like unto the goddess of inspired poetry in wisdom and understanding), and the whole is broken, you can pretty much bet that it is Billy's modification that has broken it, and you can spot his bits straight away, this makes debugging a lot easier.
I think this is one of the more unfortunate side-effects of things like checkstyle and other forms of overly restrictive style enforcement. The more we sand-paper everybody back to the same (low) level of code appearance, the more information is lost for what I like to call "forensic debugging".
- barrkel 16y agoI strongly agree with this as well - however, when I need to overhaul a huge portion of the codebase, I may end up normalizing tabs and spacing somewhat; e.g. tabs between 'if', 'while', 'for' and '(', spaces between function / array name and '(' or '[', etc. That is to say, I don't mind everyone being free to format code how they see fit, just don't be surprised if in rewriting or modifying it, it gets "fixed" differently. I'm currently doing this right now at work, hence my vehemence. There's even things like this in class definitions: int const * const FooBar // Yes, that's a tab (Foo foo, Bar bar) which at first glance can end up looking like instance variable declarations instead of methods.