Of course it was a string of failures. I don't care if it's an oil rig or a software bug, it usually takes more than one failure before a problem actually surfaces. It's usually a combination of physical defects, human error, and process failures... but it takes the entire sequence to fail before something goes wrong.
The longer it takes for a problem to be discovered, the more failures probably exist in the chain. Honestly, I'd be more scared if only a couple things went wrong.
"Alt-D, Tab" is another way. I found that one before I knew Ctrl-K existed and now it's too late to reprogram my fingers. The problem is that IE requires two Tabs, so I might have to relearn anyway.
Although it did take them several months to get Halo off the computers. One of the upperclassmen somehow managed to get the game on the master ISO they used to reformat. So every time they wiped the drive in an attempt to remove it, they were actually reinstalling it.
Brilliant! Look in the yearbook under "Most likely to hack a government computer system" for the culprit.
'course, given consumer credit card debt levels, it's painfully clear most lack those skills, and are unable or unwilling to acquire them.
Or, they're using credit to pretend they make more money than they really do. This buys them happiness for a while, but then the debt becomes an additional worry on top of everything else.
"Money can't buy happiness. But it can buy a boat and invite happiness over for a weekend."
The key is to make enough money that you don't have to worry about money. Cost of living and family size definitely plays into that. The hard part is defining what worrying about money entails, but I would think 75k is a reasonable US average.
Mr. Burns: Smithers, why haven't I heard of this "The Leader"? He's as rich and wicked as I, but he seems to enjoy tax exempt status! Smithers: Actually, sir, with our creative book-keeping and corporate loop holes we only pay three dollars a year. Mr. Burns: [Shocked] You're right, we're getting screwed!
These women were apparently fine with abortions beforehand, but the emotional impact only hit them afterwords. They didn't know they didn't like them when they had one. That's a big problem, in my book.
Abortions shouldn't be illegal just because the parents might regret it later, but I think education beforehand is an absolute must.
Ahhh. I forgot about the macro problem. I wish I could mod you up, but that's against the rules.
For those not in the know, macros are interpreted very literally by the preprocessor. A macro with multiple lines in it generally requires a stupid trick like enclosing the code within a do {... } while(0) to prevent just this problem. Or a if (true) {...} else (void)0.
It gets downright nasty when it's time to peer review code. More time is spent pointing out bad spacing and typos in comments than actual problems with the code.
Programmers can get picky and religious if the code isn't formatted just so. Vertical alignment of variable declarations/initializations are one such case: there's no reason to codify this in a document, but opinions vary. Do you align the '=', the variable name, or both? How do you deal with pointers? References?
Ugh... I hate it. And yet... I have my own opinions and defend them on occasion. I'm part of the problem.
The reality is that a programmer should be able to deal with just about any coding style. Consistency is good, and some things are downright dangerous, of course... but you should still be able to work with it.
This is part of nearly every coding standard I've seen.
And yet, I've never actually seen a bug caused by it when this rule isn't enforced.
Maybe it's because people actually use sane editors now which automatically indent for you. That certainly makes the problem easier to spot.
Or maybe it's because people train their eyes to notice the problem, making this only a good rule for those that have followed it for their entire careers.
Or maybe I've just been lucky. Who knows.
But I do agree with you that it's stupid how much discussion revolves around such a simple thing. People get downright religious about braces and indenting during peer reviews. That alone makes me want to find a new job sometimes.
Slashdot Mirror
The suggestions must be ranked by popularity. After all, nobody looks for porn on the internet, right?
Of course it was a string of failures. I don't care if it's an oil rig or a software bug, it usually takes more than one failure before a problem actually surfaces. It's usually a combination of physical defects, human error, and process failures ... but it takes the entire sequence to fail before something goes wrong.
The longer it takes for a problem to be discovered, the more failures probably exist in the chain. Honestly, I'd be more scared if only a couple things went wrong.
"Alt-D, Tab" is another way. I found that one before I knew Ctrl-K existed and now it's too late to reprogram my fingers. The problem is that IE requires two Tabs, so I might have to relearn anyway.
Don't worry. It's just a phase.
Although it did take them several months to get Halo off the computers. One of the upperclassmen somehow managed to get the game on the master ISO they used to reformat. So every time they wiped the drive in an attempt to remove it, they were actually reinstalling it.
Brilliant! Look in the yearbook under "Most likely to hack a government computer system" for the culprit.
Never attribute to malice that which is adequately explained by an attempt at education? Somehow that just doesn't feel right.
My first Whoosh on Slashdot. That should be one of the achievements.
'course, given consumer credit card debt levels, it's painfully clear most lack those skills, and are unable or unwilling to acquire them.
Or, they're using credit to pretend they make more money than they really do. This buys them happiness for a while, but then the debt becomes an additional worry on top of everything else.
"Money can't buy happiness. But it can buy a boat and invite happiness over for a weekend."
Interesting point. Credit cards can artificially increase spending ability beyond what an income can technically support.
That implies that credit can buy happiness up until the consumer overextends their credit.
The key is to make enough money that you don't have to worry about money. Cost of living and family size definitely plays into that. The hard part is defining what worrying about money entails, but I would think 75k is a reasonable US average.
Why don't you *******s shut the ******* up!
You must have used some really foul language. Slashdot never censors posts like that!
You're obviously in denial. The first step is admit this, so repeat after me:
"Hi, my name is CAIMLAS and I'm an alcoholic."
Strangely appropriate sig, by the way.
Mr. Burns: Smithers, why haven't I heard of this "The Leader"? He's as rich and wicked as I, but he seems to enjoy tax exempt status!
Smithers: Actually, sir, with our creative book-keeping and corporate loop holes we only pay three dollars a year.
Mr. Burns: [Shocked] You're right, we're getting screwed!
Indeed. The Streisand Effect is quite powerful, and there's nobody to sue over it.
Oh, great. Now he's going to sue Slashdot!
Keep your comments to yourself next time.
"If you don't like abortions, don't have one."
These women were apparently fine with abortions beforehand, but the emotional impact only hit them afterwords. They didn't know they didn't like them when they had one. That's a big problem, in my book.
Abortions shouldn't be illegal just because the parents might regret it later, but I think education beforehand is an absolute must.
But isn't a cucumber that small called a gherkin?
(...waits for the Offtopic mod instead of Funny...)
This more or less always works.
You're not joking: it even makes the Time Cube site somewhat readable!
Whitespace.
Well, that certainly explains some of their logos.
I see it as a case for avoiding macros, especially the multi-line variety.
The best solution might be both.
Ahhh. I forgot about the macro problem. I wish I could mod you up, but that's against the rules.
For those not in the know, macros are interpreted very literally by the preprocessor. A macro with multiple lines in it generally requires a stupid trick like enclosing the code within a do { ... } while(0) to prevent just this problem. Or a if (true) {...} else (void)0.
Ugh. See this for more info.
And? Do you think I haven't seen this countless times when I was making the point?
No pun intended, I suppose?
It gets downright nasty when it's time to peer review code. More time is spent pointing out bad spacing and typos in comments than actual problems with the code.
Programmers can get picky and religious if the code isn't formatted just so. Vertical alignment of variable declarations/initializations are one such case: there's no reason to codify this in a document, but opinions vary. Do you align the '=', the variable name, or both? How do you deal with pointers? References?
Ugh ... I hate it. And yet ... I have my own opinions and defend them on occasion. I'm part of the problem.
The reality is that a programmer should be able to deal with just about any coding style. Consistency is good, and some things are downright dangerous, of course ... but you should still be able to work with it.
This is part of nearly every coding standard I've seen.
And yet, I've never actually seen a bug caused by it when this rule isn't enforced.
Maybe it's because people actually use sane editors now which automatically indent for you. That certainly makes the problem easier to spot.
Or maybe it's because people train their eyes to notice the problem, making this only a good rule for those that have followed it for their entire careers.
Or maybe I've just been lucky. Who knows.
But I do agree with you that it's stupid how much discussion revolves around such a simple thing. People get downright religious about braces and indenting during peer reviews. That alone makes me want to find a new job sometimes.