[..] he pressure exerted on a body 10m under the surface in the ocean is higher, but only because salt water is denser than fresh water [..]
BZZZZZZZZZTT!!!!!!!!!
Sorry! Thanks for playing our game though -- what do we have as a parting gift for him, Glen?
Well he'll be able to finally do his science homework, Tom, because we're sending him home with the entire library of Mr. Wizard's World DVDs! Maybe next time, eh?
When I opened up my Grandma's brain to install the update (::cough,cough:: whoa, dusty!!! ), everything seemed to go alright... at first... things just started going downhill not too long after I got the thumbscrews back in...
Yeah. Frequent, unexpected shutdowns/crashes. Memory leaking all over the place. Some peripherals seem to be completely unaddressable, others seem to have had their drivers corrupted as they work in spasms. Half the time she's completely unresponsive, maybe some I/O call is failing and causing a block, who knows...
Oh, well. She's an old system, no docs or anything, and her service warranty expired looooong ago. I think I've narrowed it down to being an issue where the filesystem got mucked up, but considering her age it could literally be anything...
Just to be sure, I should drive her up to that big-box store uptown to see what it'd take to get her all patched up and running again (they'll overcharge, though, hrmf..). OOH, wait! I heard they have some service where you ring them up and a couple technicians in funny little techie uniforms cruise over in their special little techie van and pick it up for you! Bonus! Where's that number...
No, his aim is fine. It's his ping time that is the problem. Jerry Fallwell had just been ludicrously evil for longer than Jack Thompson has, and (due to the stupid hardcoded speed-of-light thing**) it currently takes a couple decades to establish a TCP (Thunderbolt-Chucking Protocol) socket over ether. Oh, and don't even get him started on packet collisions between other deities on the network, either...
(** -- It was the night before the big presentation to the department heads, and it was between fixing that or the 'vaginas-might-grow-fangs' bug...)
Gawd, dude, read the source -- the code is self-documenting...
In the argument list for the CBaby constructor, if the 2nd argument ( CMale& babyDaddy) isn't specified it uses a default one, which has all its member variables initialized to their respective defaults -- usually zero.
Or did you forget that 'color:#000000' and 'color:black' are the same thing?
They're not. They're not making a cent by playing music (legally, anyway). If a radio station stopped playing music by the Supremes, it is very likely that the station would notice a zero-point-zero-zero-percent drop in revenue as a result.
Why?
Stations only make money from advertisements. And last I checked, the Supremes aren't going to be Right Guard Anti-Perspirant spokespeople any time soon...
Re:easy distribution get you market shares
on
Piracy Economics
·
· Score: 1
Bugs often cause (or mask) more problems than the issue causing the bug to be fixed. In other words, fixing a bug causing a known issue can also fix several unknown issues
Good sir! I parry your thrust and counter with a dazzling riposte :
Fixing a trivial or otherwise low-priority bug can also potentially break portions of the system that work acceptably with the bug as-is, due to unforseen or difficult-to-reproduce entanglements. The newly-created bugs in the previously-stable systems could potentially be showstoppers or feature-breakers.
Yes, I paint a very grim, very cynical picture of how to view a codebase; however, in a world where departments already over-exert the engineering team simply to make delivery milestones and there's not a single man-minute that isn't already double-booked in the schedule, it is not quite as clear-cut, black-and-white of a scenario as some people like to pretend.
Is it wise to risk silently breaking some component and not finding out about it until much later -- perhaps you only find it 19 hours, 7 pots of coffee, and 39 phone calls from your nagging wife after the fury began : angry manager emails flooded your inbox because the current software build inexplicably failed its required quarterly standards compliance audit and that asshat Todd guy ("Jerkwad Todd"... everyone totally hates that jerk) who wrote the "bug fix" in question [a] documented his hard work by bellyaching in the javadoc stub about how writing the patch was totally like beneath him and how the last job he had was like so much more challenging and meaningful, and [b] was evidently terminated by the company roughly 5 1/2 weeks ago -- all because of a corner-case?
Remember, every time a line of code is inserted, deleted, moved, or modified, there exists the possibility that a bug will be introduced. It is sometimes in the best (short-term) interests of an organization (especially one that is developing closed-source software) to pick their battles when it comes to "fixing" things -- especially when the problem is never/rarely noticed by stakeholders. Not always, of course. But sometimes.
It just so happens that it is time travel, poncho! Wanna know the best part? Since I'm obviously going to succeed -- I mean, come on -- I don't have to start principal research or development for like years!!!!
Slashdot Mirror
Only if everyone at work refers to you as "Lieutennant" or "Mr. Assistant District Attourney" or something.
Otherwise you should be good to go.
BZZZZZZZZZTT!!!!!!!!!
Sorry! Thanks for playing our game though -- what do we have as a parting gift for him, Glen?
Well he'll be able to finally do his science homework, Tom, because we're sending him home with the entire library of Mr. Wizard's World DVDs! Maybe next time, eh?
Maybe indeed, Glen!
> ..the easiest deterent of overpopulation is perhaps technological proliferation..
::also giggled at "particularly neat" but not everyone is quite drunk enough for punnery, and I don't have much karma::
Interesting word choices, given the topic article's general premise and when talking about a population reduction c/o advanced technology...
MY BODY -- MY CHOICE!
Because it's been a tradition to do so in this country : November of 2000, November of 2004, every election in between, and every single day since.
You must be new here... Welcome to Software Development!
Well, luckily my wife doesn't need to be shocking. She's mute.
Speaking as a guitar player, my mind just asploded.
Sure, sure, but lest you forget!
All some hacker needs to do is drop a 128-bit logic bomb right down our SCSI valve, and we'd be done for!
I mean, seven monitors!
Oh, you will. But don't worry.
::recommends the veal::
They provide patches that'll do that for you...
Who said what now 'bout us turnin' our back?
Boy, I only done stopped that thar shootin' fer cuz I's be born fer WRASSLIN' !!!!!
When I opened up my Grandma's brain to install the update ( ::cough,cough:: whoa, dusty!!! ), everything seemed to go alright... at first... things just started going downhill not too long after I got the thumbscrews back in...
Yeah. Frequent, unexpected shutdowns/crashes. Memory leaking all over the place. Some peripherals seem to be completely unaddressable, others seem to have had their drivers corrupted as they work in spasms. Half the time she's completely unresponsive, maybe some I/O call is failing and causing a block, who knows...
Oh, well. She's an old system, no docs or anything, and her service warranty expired looooong ago. I think I've narrowed it down to being an issue where the filesystem got mucked up, but considering her age it could literally be anything...
Just to be sure, I should drive her up to that big-box store uptown to see what it'd take to get her all patched up and running again (they'll overcharge, though, hrmf..). OOH, wait! I heard they have some service where you ring them up and a couple technicians in funny little techie uniforms cruise over in their special little techie van and pick it up for you! Bonus! Where's that number...
Milorad Blagojevich --> I Am Lord Vaji-Go-Belch
...I knew it!
No, his aim is fine. It's his ping time that is the problem. Jerry Fallwell had just been ludicrously evil for longer than Jack Thompson has, and (due to the stupid hardcoded speed-of-light thing**) it currently takes a couple decades to establish a TCP (Thunderbolt-Chucking Protocol) socket over ether. Oh, and don't even get him started on packet collisions between other deities on the network, either...
(** -- It was the night before the big presentation to the department heads, and it was between fixing that or the 'vaginas-might-grow-fangs' bug...)
I am teh wniner!!!
Gawd, dude, read the source -- the code is self-documenting...
In the argument list for the CBaby constructor, if the 2nd argument ( CMale& babyDaddy ) isn't specified it uses a default one, which has all its member variables initialized to their respective defaults -- usually zero.
Or did you forget that 'color:#000000' and 'color:black' are the same thing?
Newbs...
They're not. They're not making a cent by playing music (legally, anyway). If a radio station stopped playing music by the Supremes, it is very likely that the station would notice a zero-point-zero-zero-percent drop in revenue as a result.
Why?
Stations only make money from advertisements. And last I checked, the Supremes aren't going to be Right Guard Anti-Perspirant spokespeople any time soon...
Indentation is
a privilege
it is not
a right.
Well, yeah, DUH ! Everyone knows that !
Fixing a trivial or otherwise low-priority bug can also potentially break portions of the system that work acceptably with the bug as-is, due to unforseen or difficult-to-reproduce entanglements. The newly-created bugs in the previously-stable systems could potentially be showstoppers or feature-breakers.
Yes, I paint a very grim, very cynical picture of how to view a codebase; however, in a world where departments already over-exert the engineering team simply to make delivery milestones and there's not a single man-minute that isn't already double-booked in the schedule, it is not quite as clear-cut, black-and-white of a scenario as some people like to pretend.
Is it wise to risk silently breaking some component and not finding out about it until much later -- perhaps you only find it 19 hours, 7 pots of coffee, and 39 phone calls from your nagging wife after the fury began : angry manager emails flooded your inbox because the current software build inexplicably failed its required quarterly standards compliance audit and that asshat Todd guy ("Jerkwad Todd"... everyone totally hates that jerk) who wrote the "bug fix" in question [a] documented his hard work by bellyaching in the javadoc stub about how writing the patch was totally like beneath him and how the last job he had was like so much more challenging and meaningful, and [b] was evidently terminated by the company roughly 5 1/2 weeks ago -- all because of a corner-case?
Remember, every time a line of code is inserted, deleted, moved, or modified , there exists the possibility that a bug will be introduced. It is sometimes in the best (short-term) interests of an organization (especially one that is developing closed-source software) to pick their battles when it comes to "fixing" things -- especially when the problem is never/rarely noticed by stakeholders. Not always, of course. But sometimes.
It just so happens that it is time travel, poncho! Wanna know the best part? Since I'm obviously going to succeed -- I mean, come on -- I don't have to start principal research or development for like years!!!!
Suckers!
In Soviet Russia, punchline forgets you!
FA
::snicker, snicker::
I can see the marketing now...
Now you're playing with power...Superpower!
And why's he always telling me what to do?