Software patents are like patenting the plans to make a house. Anyone who makes a house (even using alternative plans that make something like a house) would be in violation of said patent.
You don't need cell cameras or any fancy in car system. Bury those vehicle sensors a set distance apart. You collect your data, no names/photos/profiling are attached...
I was reading that some states (California?) actually do use these street sensors to determine if a speeding vehicle is coming and triggers the lights to try to make them stop. I would imagine people would get used ot the timing and speed up to avoid getting caught in the light... but anyway.
I always had a problem with speeding tickets because of this imaginary "threshold." If I'm driving 70MPH and everyone else is doing 67MPH in a 65MPH zone... how is it that I am the only one ticketed? Isn't the immediate consensus of everyone else on the road at that time that the speed limit is unjust or improper? Shouldn't it be a requirement that all offenders be ticketed and not just the one picked out of the herd?
"Woooo!!!!" *waving arms running to one side of the stage* "Woooo!!!!" *waving arms running back to the other side of the stage* "Woooo!!!!" *waving arms running to middle of the stage* "Woooo!!!!" *standing at the podium drenched in sweat*
You don't write comments to let people know that you're looping over an array, you write comments to let people know WHY you're looping over an array and why they should care.
getItemsWithValueOver(array, minValue) { for(...
There's your why. As far as if they should care? I don't know if there's any reason I can make anyone care, but I'm guessing they should care because you use the value(s) later.
importSettings(... <-- what it's doing importSettings(settingsFile, sqlNode); <-- why it's importing the settings... you need the sql node of the settings file Also, can be written as (depending on the language, etc): sqlNode = importSettings(settingsFile).sqlNode;
It also relies on the coder trusting that the comment is accurate. Are you writing a program to do a specific task or writing comments to do that task? I put more faith in the code (because that's what the compiler runs) over the comment. If the comment says one thing and the code does something else, I'm willing to bet the code is more accurate. If I rewrite the code to match the comment, I may have just re-introduced an old bug. Now I have to go back through the file history to figure out if this was changed and/or if the original author was a poor commenter.
Hyperlinking relies on the content remaining in that same location and if said documents ever move... all your links now need to be updated adding another layer of busywork to coding.
But what if it does the correct calculation, but the person who wrote the comment didn't fully understand (or couldn't accurately articulate) what it was doing?
Now you have two factors of confusion; Did the commenter part of the person know what they were doing (Did they properly write down what it's actually doing?) or did the coder part of the person know? What if they knew how to code up the solution, but explaining it was harder to do without using code. Maybe the code is correct, but the comment leaves out a key point. Now you assume that the code is obviously incorrect because the comment doesn't mention something.
Honestly... how much code have you written that's really that complex? Most of the stuff you probably do day in and day out is trivial by most standards.
Otherwise, the comments end up being a ton of useless bloat that just makes things harder to understand, not easier.
This right here is more of the reason I completely skip comments when reading code. I haven't read much code where the comments put any valuable content that the code didn't explain better.
Slashdot Mirror
Software patents are like patenting the plans to make a house. Anyone who makes a house (even using alternative plans that make something like a house) would be in violation of said patent.
You don't need cell cameras or any fancy in car system. Bury those vehicle sensors a set distance apart. You collect your data, no names/photos/profiling are attached...
I was reading that some states (California?) actually do use these street sensors to determine if a speeding vehicle is coming and triggers the lights to try to make them stop. I would imagine people would get used ot the timing and speed up to avoid getting caught in the light... but anyway.
I always had a problem with speeding tickets because of this imaginary "threshold." If I'm driving 70MPH and everyone else is doing 67MPH in a 65MPH zone... how is it that I am the only one ticketed? Isn't the immediate consensus of everyone else on the road at that time that the speed limit is unjust or improper? Shouldn't it be a requirement that all offenders be ticketed and not just the one picked out of the herd?
Besides... do you think they'd show everyone how to defeat a law enforcement device?
Wouldn't that be like strapping an eraser to the end of your pencil so anything you write will be cushioned by the soft rubber?
Should be easy to spot in the crowd with the large L shaped bulge in the throat.
RGB : http://www.nationalmediamuseum.org.uk/PlanAVisit/Exhibitions/LeeAndTurner.aspx
"Woooo!!!!" *waving arms running to one side of the stage*
"Woooo!!!!" *waving arms running back to the other side of the stage*
"Woooo!!!!" *waving arms running to middle of the stage*
"Woooo!!!!" *standing at the podium drenched in sweat*
OS X Kitten, warm as a mitten?
But could you imagine coming across a QR code as a historian and trying to figure out what it means?
I was thinking RIP.com
It's perfectly normal to have to edit the registry to show/hide parts of the UI!
And if the comment is wrong?
You don't write comments to let people know that you're looping over an array, you write comments to let people know WHY you're looping over an array and why they should care.
getItemsWithValueOver(array, minValue) { for(...
There's your why. As far as if they should care? I don't know if there's any reason I can make anyone care, but I'm guessing they should care because you use the value(s) later.
Proper naming can explain what and why...
importSettings(... <-- what it's doing
importSettings(settingsFile, sqlNode); <-- why it's importing the settings... you need the sql node of the settings file
Also, can be written as (depending on the language, etc):
sqlNode = importSettings(settingsFile).sqlNode;
The 'how' is the method itself.
What if you can write your code so that every method is incredibly basic?
It also relies on the coder trusting that the comment is accurate. Are you writing a program to do a specific task or writing comments to do that task? I put more faith in the code (because that's what the compiler runs) over the comment. If the comment says one thing and the code does something else, I'm willing to bet the code is more accurate. If I rewrite the code to match the comment, I may have just re-introduced an old bug. Now I have to go back through the file history to figure out if this was changed and/or if the original author was a poor commenter.
Hyperlinking relies on the content remaining in that same location and if said documents ever move... all your links now need to be updated adding another layer of busywork to coding.
What if what they meant to write would give the wrong result, but the code they wrote is correct?
But what if it does the correct calculation, but the person who wrote the comment didn't fully understand (or couldn't accurately articulate) what it was doing?
Now you have two factors of confusion; Did the commenter part of the person know what they were doing (Did they properly write down what it's actually doing?) or did the coder part of the person know? What if they knew how to code up the solution, but explaining it was harder to do without using code. Maybe the code is correct, but the comment leaves out a key point. Now you assume that the code is obviously incorrect because the comment doesn't mention something.
Honestly... how much code have you written that's really that complex? Most of the stuff you probably do day in and day out is trivial by most standards.
Otherwise, the comments end up being a ton of useless bloat that just makes things harder to understand, not easier.
This right here is more of the reason I completely skip comments when reading code. I haven't read much code where the comments put any valuable content that the code didn't explain better.
Until the resource no longer exists.
I think the cooler magic carpet would inflate to cushion a fall.
Dogs can't talk so one laying on the carpet may pose problems for that scenario.