Code, women do it better
-
new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code.
I am going to pretty much validate what this article says[^] but that is one horrible coding standard, in my humble opinion. The "change history" bit is particularly nasty. We have source control and commit comments for that.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
Having it in source control is all fine and dandy, but when you've retrieved code from source control and you're scanning through it in the IDE, it's really nice to have those coding standards in place. That's the way I like to comment my code - especially when you're in a team of programmers.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Having it in source control is all fine and dandy, but when you've retrieved code from source control and you're scanning through it in the IDE, it's really nice to have those coding standards in place. That's the way I like to comment my code - especially when you're in a team of programmers.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001You do change history in comments?
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
You do change history in comments?
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
I do, when working on shared code, but quite informally. I also like the easy availability in the IDE.
Anyone wanting my sympathy need not ask.
-
//10.29.2008 The shoes didn't fit well so i had to return them. But it like totally worked out //because now they had the green ones in stock.. they are sooo amazing //oh and added a check for null
i was really nice in my joke...because after watching sex and the city the movie im really worried about what kind of content these "comments" would carry...
----------------------------------------------------------- "When I first saw it, I just thought that you really, really enjoyed programming in java." - Leslie Sanford
-
I do, when working on shared code, but quite informally. I also like the easy availability in the IDE.
Anyone wanting my sympathy need not ask.
Ditto. We do it informally with a <revision> tag in the the XML documention. Not for every little change, only significant changes: things like bug fixes, new functionality, new logic, etc. Renaming a variable or introduciing a new local isn't worthy of a revision notice.
Life, family, faith: Give me a visit. From my latest post: "How differently the psalmist saw it! How blessed -- how truly happy with real joy! -- is the man who delights in the Law of the Lord." Judah Himango
-
new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code.
I am going to pretty much validate what this article says[^] but that is one horrible coding standard, in my humble opinion. The "change history" bit is particularly nasty. We have source control and commit comments for that.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
Girls are also the solution to poverty, AIDS, hunger, war and such.[^]
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
Girls are also the solution to poverty, AIDS, hunger, war and such.[^]
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
Let's not diss them too much though. They're just so much nicer to errm, cuddle.... (I'll let you replace the word with the physical action of your choice). Let's face it, for all their naive statements about comments and the like, they are a better choice than the alternative.
Deja View - the feeling that you've seen this post before.
-
Girls are also the solution to poverty, AIDS, hunger, war and such.[^]
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
"The world is a complete mess. Agree or disagree." Disagree. "Really? 600 Million girls would disagree with you." Good for them! Closes browser window.
-
"The world is a complete mess. Agree or disagree." Disagree. "Really? 600 Million girls would disagree with you." Good for them! Closes browser window.
I pretty much agree. In Africa especially. Women solve a lot more problems than the men but they get a lot less support.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
-
I pretty much agree. In Africa especially. Women solve a lot more problems than the men but they get a lot less support.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
Paul Watson wrote:
Women solve a lot more problems than the men but they get a lot less support.
Yeah, well they'd be advised not knocking on my door for it either. There's one women who gets my support and that's my duty done as far as I'm concerned :)
-
new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code.
I am going to pretty much validate what this article says[^] but that is one horrible coding standard, in my humble opinion. The "change history" bit is particularly nasty. We have source control and commit comments for that.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
I find that anyone who assigns an ethnicity, or gender classification to subject matter that are totally unrelated, suspect, anything they write I therefore discounted. examples of stupidity; Hey you are black, you can dance... All white women are molleys[^]... All Jews are good at accounting... ... I bet you can't fool ole Rebecca Buckman, when she walks into a room, I bet she immediately knows if you are black, white, man, are a women and she's got you all figured out and what your capabilities are. [modified added link to what a molley is /]
MrPlankton
modified on Saturday, June 7, 2008 8:48 AM
-
I find that anyone who assigns an ethnicity, or gender classification to subject matter that are totally unrelated, suspect, anything they write I therefore discounted. examples of stupidity; Hey you are black, you can dance... All white women are molleys[^]... All Jews are good at accounting... ... I bet you can't fool ole Rebecca Buckman, when she walks into a room, I bet she immediately knows if you are black, white, man, are a women and she's got you all figured out and what your capabilities are. [modified added link to what a molley is /]
MrPlankton
modified on Saturday, June 7, 2008 8:48 AM
MrPlankton wrote:
examples of stupidity; Hey you are black, you can dance... All white women are Molleys... All Jews are good at accounting... ...
All Geordie's are heavy drinkers. Damn - she nailed that one. How about, "All men think about sex"? Damn. No, she got that one right as well.
Deja View - the feeling that you've seen this post before.
-
new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code.
I am going to pretty much validate what this article says[^] but that is one horrible coding standard, in my humble opinion. The "change history" bit is particularly nasty. We have source control and commit comments for that.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
McGrattan boasts that 70% to 80% of the time, she can look at a chunk of computer code and tell if it was written by a man or a woman.
Considering that maybe more than 80% of programmers are men, anybody can boast that with 70% to 80% accuracy.
My .NET Business Application Framework My Home Page My Younger Son & His "PET"
modified on Sunday, June 8, 2008 6:05 AM
-
[Quote]In an effort to make Ingres’s computer code more user-friendly and gender-neutral, McGrattan helped institute new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code. The rules apply to both Ingres employees and members of the open-source community who contribute code to Ingres’s products.[/Quote] Yup - I've used Ingres' database - it's one of the nastiest pieces of database technology that it's ever been my misfortune to touch. While other database manufacturers actually went about making their databases more powerful and useful, Ingres is better commented. :rolleyes:
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
one of the nastiest pieces of database technology
Indeed. Fortunately last fall we replaced the third-party product that uses it. Unfortunately the new third-party product uses Caché, which may be even worse. Developer of the new product: "But it's Faaasssst!" X|
-
Pete O'Hanlon wrote:
one of the nastiest pieces of database technology
Indeed. Fortunately last fall we replaced the third-party product that uses it. Unfortunately the new third-party product uses Caché, which may be even worse. Developer of the new product: "But it's Faaasssst!" X|
PIEBALDconsult wrote:
Developer of the new product: "But it's Faaasssst!"
Yup - it crashes faster than ever.
Deja View - the feeling that you've seen this post before.
-
McGrattan boasts that 70% to 80% of the time, she can look at a chunk of computer code and tell if it was written by a man or a woman.
Considering that maybe more than 80% of programmers are men, anybody can boast that with 70% to 80% accuracy.
My .NET Business Application Framework My Home Page My Younger Son & His "PET"
modified on Sunday, June 8, 2008 6:05 AM
Excellent point. I also fear that she would like at my code declare that it was written by a woman. Not that there's anything wrong with that.
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
-
Girls are also the solution to poverty, AIDS, hunger, war and such.[^]
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
I guess I should go get a few.
-
new coding standards at the company. They require programmers to include a detailed set of comments before each block of code explaining what the piece of code does and why; developers also must supply a detailed history of any changes they have made to the code.
I am going to pretty much validate what this article says[^] but that is one horrible coding standard, in my humble opinion. The "change history" bit is particularly nasty. We have source control and commit comments for that.
regards, Paul Watson Ireland & South Africa
Fernando A. Gomez F. wrote:
At least he achieved immortality for a few years.
I'm with you on "change history" in source control. Each code file should have just code and comments that help understand the current code, nothing else. If you really want that in the file, even VSS will automatically put those comments into each file for you. If the revision history is that important, then there is that code historian product for that. It gives you a color coded view of the file where each color represents the latest revision for that line. That plus viewing the file color coded for number of revisions per line and the like makes it really useful for learning a codebase.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Excellent point. I also fear that she would like at my code declare that it was written by a woman. Not that there's anything wrong with that.
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
could you lose man points...
----------------------------------------------------------- "When I first saw it, I just thought that you really, really enjoyed programming in java." - Leslie Sanford
