// TODO: fix this
Not all comments give you a mile high view. Some are just pointless wastes of disk space...
I don't see anything wrong with flagging a section of code with "TODO"... It at least let's the next person know that the code might be incomplete/buggy
It depends what you mean "real evidence" and "significant scale". I grew up partially in the country and I've seen first hand things that I would rather not have, but no, I haven't performed any in-depth studies on the matter.
Here's the thought process: "since this milk will be pasteurized, it's ok if I include milk from this sick cow over here". Are you suggesting that this train of thought isn't widespread? Beyond this particular application?
Heat pasteurization of milk, which means heating the milk to a certain temperature for a prescribed length of time, kills the TB bacteria found in the milk and makes it safe for humans to drink.
The pasteurization of milk was implemented specifically to destroy common pathogens found in raw milk and, secondarily, to give milk a longer shelf life by reducing the number of spoilage-causing organisms. Even under the strictest conditions, cows naturally carry certain disease-causing bacteria which may be passed to the milk that they produce, including Salmonella, Campylobacter, Listeria, Tuberculosis and E.coli 0157:H7.
Pasteurization is the process that allows farmers to subject their milk producing cattle to the poor conditions that produce poor milk - they feel they can get away with things that they wouldn't be able to without it, like mastitis, tuberculosis, feces contamination, etc.
Or they could slow down, and write less code, more carefully.
Mosts developers are not able to tell their boss or client that they want to "slow down, and write less code, more carefully" if they want to keep their jobs.
I like the part where you left out what they were responding to.
The part where it was suggested to fine companies that allow bad code, which would be a motivation for the boss/client to allow the developers to slow down and write less code, more carefully.
Leaving that out makes your argument much stronger.
I'm no expert here but I think the general market embraces FOSS software.
No, the general market embraces software which works for them.
No, the general market uses the software that comes with the computer when they buy it, unless it's really bad (like some disk burning utilities, etc).
The software that comes pre-installed on most systems isn't FOSS due to inside bundling deals, not due to the quality of the software.
In formal English, the date has always been written out as "...on Saturday the fourteenth of March, two thousand nine, at three o'clock in the afternoon" (as in an invitation). Note that the year is a parenthetical phrase set off by commas. In less formal writing with the slash abbreviation this becomes "...on Sat 3/14, 2009, at 3:00 pm" which is a form that has been in use in the USA before there was a USA.
Okay... So Saturday the fourteenth of March, two thousand nine contracts to Sat 3/14, 2009?
Why exactly did the day and month switch places? I'm not sure how this fits with the rest of your argument...
Yes, I was saying that hacker was mistaken, and that you had originally used the correct uppercase 'i' option.
The lowercase 'i' option for hdparm does report information, but not useful for this situation, so in that sense the double oops applies to hacker's comment.
Slashdot Mirror
Sears catalogue, biatch!
It is on my network!
// TODO: fix this Not all comments give you a mile high view. Some are just pointless wastes of disk space...
I don't see anything wrong with flagging a section of code with "TODO"... It at least let's the next person know that the code might be incomplete/buggy
Yahoo PlaceFinder does address tokenization down to the subdwelling (floor/unit level) that I haven't found in any other service.
It depends what you mean "real evidence" and "significant scale". I grew up partially in the country and I've seen first hand things that I would rather not have, but no, I haven't performed any in-depth studies on the matter.
Here's the thought process: "since this milk will be pasteurized, it's ok if I include milk from this sick cow over here". Are you suggesting that this train of thought isn't widespread? Beyond this particular application?
Here's a somewhat longer article that to me backs up the idea: http://www.york.ca/Departments/Health+Services/Raw+Milk.htm
I'm quite comfortable with the logic.
Pasteurization is the process that allows farmers to subject their milk producing cattle to the poor conditions that produce poor milk - they feel they can get away with things that they wouldn't be able to without it, like mastitis, tuberculosis, feces contamination, etc.
You take your wives to government controlled hospitals to give birth? You're part of the problem...
Or they could slow down, and write less code, more carefully.
Mosts developers are not able to tell their boss or client that they want to "slow down, and write less code, more carefully" if they want to keep their jobs.
I like the part where you left out what they were responding to.
The part where it was suggested to fine companies that allow bad code, which would be a motivation for the boss/client to allow the developers to slow down and write less code, more carefully.
Leaving that out makes your argument much stronger.
Thing is, I usually have three people sleeping about 8' from me when I'm READING frickin stuff on the internet, so I dont want video and sound.
Mute?
What, no mention of metal-halide lamps? Not a very comprehensive article...
Oxemondo is right
Someone please mod parent "whoosh!"
"uninfected" != "infected". You sure mouth off a lot for a dumbass...
I'm guessing your tinfoil hat isn't wireless...
I would assume you're referring to Open Source Ecology: http://opensourceecology.org/
I'm no expert here but I think the general market embraces FOSS software.
No, the general market embraces software which works for them.
No, the general market uses the software that comes with the computer when they buy it, unless it's really bad (like some disk burning utilities, etc).
The software that comes pre-installed on most systems isn't FOSS due to inside bundling deals, not due to the quality of the software.
promise
to represent your interests to the best of my ability!
I, for one, welcome our outdated meme perpetuating overlords!
Well I'm Canadian, and we did our part in 1814: http://en.wikipedia.org/wiki/Burning_of_Washington
Insects hate anthropomorphization.
In formal English, the date has always been written out as "...on Saturday the fourteenth of March, two thousand nine, at three o'clock in the afternoon" (as in an invitation). Note that the year is a parenthetical phrase set off by commas. In less formal writing with the slash abbreviation this becomes "...on Sat 3/14, 2009, at 3:00 pm" which is a form that has been in use in the USA before there was a USA.
Okay... So Saturday the fourteenth of March, two thousand nine contracts to Sat 3/14, 2009? Why exactly did the day and month switch places? I'm not sure how this fits with the rest of your argument...
Yes, I was saying that hacker was mistaken, and that you had originally used the correct uppercase 'i' option. The lowercase 'i' option for hdparm does report information, but not useful for this situation, so in that sense the double oops applies to hacker's comment.
Oops yourself, it's an uppercase 'i', not a lowercase 'l'.