November 14, 2015 at 5:16 am
Comments posted to this topic are about the item Mind your Database Ps and Qs
November 14, 2015 at 6:03 am
Louis, your editorial is a great elaboration of what I meant by my comment about my great Aunt Betsy's critiques of my table manners in a comment on last week's editorial.
http://www.sqlservercentral.com/Forums/FindPost1734634.aspx
As you say, anybody can do anything with SQL (pretty much), but good manners mean showing respect to your peers by HOW you do it. Just the golden rule in action. Do it the way you'd like to see it if someone else did it.
In theory, theory and practice are the same. In practice, they are not.
November 14, 2015 at 10:11 am
I've picked up several people's work many times throughout my career. If there is one thing that influences whether I become productive quickly or not, it's how easily I can read it and whether there is documentation that explains it.
Jay Bienvenu | http://bienv.com | http://twitter.com/jbnv
November 16, 2015 at 1:01 am
Manners come with little cost yet make life much more pleasant. There is even the joy in exuding good manners. In this analogy you can reap what you sow!!!
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 16, 2015 at 1:50 am
Hear, hear! Always leave comments, guarantee even your own code can look like it was written by someone else when you go back to it months/years later 🙂
November 16, 2015 at 3:07 am
I seem to spend half my life trying to drill this into various devs from multiple angles. It's often hard to maintain my equitable visage but of course always strive for such. When you have finished writing this procedure have a cup of tea, come back and write a comment explaining the various clauses - please, I say. Explain what your intent was in case the code does something a little different. Occasionally this works.
November 16, 2015 at 5:36 am
call.copse (11/16/2015)
I seem to spend half my life trying to drill this into various devs from multiple angles. It's often hard to maintain my equitable visage but of course always strive for such. When you have finished writing this procedure have a cup of tea, come back and write a comment explaining the various clauses - please, I say. Explain what your intent was in case the code does something a little different. Occasionally this works.
I ask (read demand) that the comments are written BEFORE any code. Capture ones intent then execute it.
Comments added afterwards tend to capture what the code says not what the coder was attempting. This makes it more likely that the comments are superfluous duplication of the code adding little to the understanding.
Either ways is polite. Neither way is just rude.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 17, 2015 at 3:05 am
Gary Varga (11/16/2015)
call.copse (11/16/2015)
I seem to spend half my life trying to drill this into various devs from multiple angles. It's often hard to maintain my equitable visage but of course always strive for such. When you have finished writing this procedure have a cup of tea, come back and write a comment explaining the various clauses - please, I say. Explain what your intent was in case the code does something a little different. Occasionally this works.I ask (read demand) that the comments are written BEFORE any code. Capture ones intent then execute it.
Comments added afterwards tend to capture what the code says not what the coder was attempting. This makes it more likely that the comments are superfluous duplication of the code adding little to the understanding.
Either ways is polite. Neither way is just rude.
Good thinking Batman - like writing tests before code I guess. I'll give it a try!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply