requires companies to inform federal law enforcement agencies if a database containing information on more than 10,000 citizens is infiltrated by hackers.
If you have enough users, does "cat/etc/passwd" count?
there's a crossover point for anyone under around 70 years-old where exponentially advancing technology will slow, stop, then reverse the biological aging disease.
Look at Linux. An operating system used by millions and every hacker in the world can get their hands on the source code. Why don't we see many viruses for Linux? Because it was implemented well.
I think you mean a GNU/Linux virus. Very little malicious Linux code relies only on kernel exploits to do their bad stuff. Credit where credit is due, and all that.;^)
Maybe it's because I haven't had my coffee yet, but when I first looked at it - I could have sworn the website you linked was http://www.migraneinnovations.com/
Narrator: A new program written by my company is shipped on time, but with bugs. The network stack locks up. The OS crashes and burns and scrambles the hard drive. Now, should we initiate a code review? Take the number of licenses in the field, A, multiply by the probable rate of failure, B, multiply by the average out-of-court settlement, C. A times B times C equals X. If X is less than the cost of a code review, we don't do one.
Business woman on plane: Are there a lot of these kinds of bugs?
Narrator: You wouldn't believe.
Business woman on plane: Which software company do you work for?
Narrator: A major one.
I liked Wordperfect 6.0. Also did a lot of my college papers on a CPM machine running WordStar. It's the main reason I use Joe in Linux. The keys are the same, pretty much.
However, I still stand by my statement. A word processor shouldn't be a big deal, because the task is does isn't a big deal. For me, using Word is just making sure that other non-technical people can open and read your documents. Other than that, I use gvim.
For someone currently using the new Office beta, and having been intimately familiar with previous versions, I'd just like to say that the learning curve is suprisingly low.
While I'm sure your familiarity is a factor, could the reason for the low learning curve also be the fact that it's a word processor?
No offense, but a word processor shouldn't really have much of a learning curve at all in the first place. The task it was created to fulfull is a simple one. Create a new document, then type. Save or print.
Statutory minimum annual leave plus public holidays
UK: 28 days (four weeks + public holidays)
US: 10 days (0 weeks + public holidays)
Maybe the reason why us folks in the US report so many sick days is that we're simply telling the boss we're sick and can't come in because there is no other way of getting the hell out of the office.
I've done it. I'll bet everyone here who lives in the US has done it too. Unfortunately with my current job I can't even do that, because the US has a new scourge: PTO. Paid time off. It's a pool of vacation and sick leave. You get sick, the days come out of the pool and your vacation time dries up. It's horrible.
In fact, I'll take it a step further. Americans get a lot of flak about how we're not very worldly. I think one of the reasons why is that we're not allowed to travel.
Honestly, it's true. We're not.
I'm a college graduate with a BSEE working what most people here would call a pretty darn good job in a good company. I have relatively high pay and what folks around here would call good benefits, leave time, etc.
I get 15 days of PTO a year. How the hell can you own a home, take care of your mundane living details and see the world on fifteen lousy days a year?
I've had entire years where I haven't even left the state I live in. No time to do so.
Well, I was kinda shooting for a joke there. "Sure it does" is one of those phrases that if you say it seriously is positive, but with a slight change of inflection is extremely negative and sarcastic. Just trying to have a little fun with the original poster, but nobody got the joke. In a way, that's kinda funny too considering the topic.
Anyway, as for the "fired if you don't understand the lunch email"...well, I agree with you in spirit. Kinda. Read the RFC for SMTP, 2821 and you'll understand my objection. Here's the important bit, from 4.5.4.1, "Sending Strategy":
In a typical system,
the program that composes a message has some method for requesting
immediate attention for a new piece of outgoing mail, while mail that
cannot be transmitted immediately MUST be queued and periodically
retried by the sender. A mail queue entry will include not only the
message itself but also the envelope information.
The sender MUST delay retrying a particular destination after one
attempt has failed. In general, the retry interval SHOULD be at
least 30 minutes; however, more sophisticated and variable strategies
will be beneficial when the SMTP client can determine the reason for
non-delivery.
In other words, if the network is busy or some other odd hiccup happens, the RFC recommends waiting a minimum of a half an hour (or possibly a lot more) before a retransmit. This is why time sensitive stuff should never be emailed - you could be fired for not showing up for that lunch, and it may not be your fault at all. I personally have seen email messages sit in a queue for as long as 2 days before my recipient receives it.
The unit numbers shouldn't matter from a success standpoint, should they? From Wikipedia:
Businessweek magazine compiled a report[1] that estimates the total cost of components in the "premium" bundle at $525 USD, sans manufacturing costs, meaning that Microsoft is losing money on every Xbox 360 system sold. It should be noted that the strategy of selling a console at a loss or near-loss is common in the console games industry, as console makers can usually expect to make up the loss through game licensing.
The console numbers that MS releases are marketing fluff to get developers hot and happy to write games for the Xbox360. The real numbers that need to be looked at to determine if this thing is a success is in numbers of games sold, and the directly related return on investment selling licensing to cover that loss.
They could sell a billion of them, but if nobody buys any games for them - the platform would financially be an epic failure.
He worked on such dogs as Apple Computer's defunct video card business, 3DO's failed game consoles, a chip startup that screwed up a deal with Nintendo, the never successful WebTV and Microsoft's canceled Ultimate TV satellite TV recorder.
What I want to know is how he keeps getting job offers. Seriously - I haven't had 1/100th this much opportunity in my whole entire life.
Slashdot Mirror
I believe you're assuming the tin can is a perfect conductor. You might want to read this.
"Now is the winter of our discontent. Or the summer of Australia's discontent. Either or. Take your pick."
requires companies to inform federal law enforcement agencies if a database containing information on more than 10,000 citizens is infiltrated by hackers.
If you have enough users, does "cat /etc/passwd" count?
Freeman Lowell, from Silent Running. And of course his assistants, Huey, Dewie and Louie.
...Lord_Dweomer =)
Happy Fun Wiki!
It's a depressing story, but a great one. I saw it as a kid and it still haunts me. Hope you like it. =)
there's a crossover point for anyone under around 70 years-old where exponentially advancing technology will slow, stop, then reverse the biological aging disease.
It's pig's bladder - read Damon Knight's Forever.
Excellent movie. Ever see any of the short-lived TV series? I did. Yup, I'm that old. Ah well.
Anyways, for extra credit, rent another film from the same era: Silent Running.
Look at Linux. An operating system used by millions and every hacker in the world can get their hands on the source code. Why don't we see many viruses for Linux? Because it was implemented well.
I think you mean a GNU/Linux virus. Very little malicious Linux code relies only on kernel exploits to do their bad stuff. Credit where credit is due, and all that. ;^)
Thank you.
Remember, in advertising-speak, "up to" means "less than". Values between 0% and 75% fulfill the conditions of being "up to a 75% savings".
Maybe it's because I haven't had my coffee yet, but when I first looked at it - I could have sworn the website you linked was http://www.migraneinnovations.com/
Good point! It's the fifth of may. Replace the lemon juice with lime juice. =)
Not even if they let you reach through the internet and castrate the spammer. With a spoon. Full of lemon juice. And margarita salt.
Without the callous disregard for loss of life, that exchange is just stupid.
Ok then, does this help?
Narrator: A new program written by my company is shipped on time, but with bugs. The network stack locks up. The OS crashes and burns and scrambles the hard drive. Now, should we initiate a code review? Take the number of licenses in the field, A, multiply by the probable rate of failure, B, multiply by the average out-of-court settlement, C. A times B times C equals X. If X is less than the cost of a code review, we don't do one.
Business woman on plane: Are there a lot of these kinds of bugs?
Narrator: You wouldn't believe.
Business woman on plane: Which software company do you work for?
Narrator: A major one.
...and it's biggest liability.
They're so damned huge that the left hand really honestly doesn't know what the right one is doing. At least it sure seems that way, doesn't it?
I liked Wordperfect 6.0. Also did a lot of my college papers on a CPM machine running WordStar. It's the main reason I use Joe in Linux. The keys are the same, pretty much.
However, I still stand by my statement. A word processor shouldn't be a big deal, because the task is does isn't a big deal. For me, using Word is just making sure that other non-technical people can open and read your documents. Other than that, I use gvim.
For someone currently using the new Office beta, and having been intimately familiar with previous versions, I'd just like to say that the learning curve is suprisingly low.
While I'm sure your familiarity is a factor, could the reason for the low learning curve also be the fact that it's a word processor?
No offense, but a word processor shouldn't really have much of a learning curve at all in the first place. The task it was created to fulfull is a simple one. Create a new document, then type. Save or print.
From the first +5 post in the thread:
Statutory minimum annual leave plus public holidays
UK: 28 days (four weeks + public holidays)
US: 10 days (0 weeks + public holidays)
Maybe the reason why us folks in the US report so many sick days is that we're simply telling the boss we're sick and can't come in because there is no other way of getting the hell out of the office.
I've done it. I'll bet everyone here who lives in the US has done it too. Unfortunately with my current job I can't even do that, because the US has a new scourge: PTO. Paid time off. It's a pool of vacation and sick leave. You get sick, the days come out of the pool and your vacation time dries up. It's horrible.
In fact, I'll take it a step further. Americans get a lot of flak about how we're not very worldly. I think one of the reasons why is that we're not allowed to travel.
Honestly, it's true. We're not.
I'm a college graduate with a BSEE working what most people here would call a pretty darn good job in a good company. I have relatively high pay and what folks around here would call good benefits, leave time, etc.
I get 15 days of PTO a year. How the hell can you own a home, take care of your mundane living details and see the world on fifteen lousy days a year?
I've had entire years where I haven't even left the state I live in. No time to do so.
Well, I was kinda shooting for a joke there. "Sure it does" is one of those phrases that if you say it seriously is positive, but with a slight change of inflection is extremely negative and sarcastic. Just trying to have a little fun with the original poster, but nobody got the joke. In a way, that's kinda funny too considering the topic.
Anyway, as for the "fired if you don't understand the lunch email"...well, I agree with you in spirit. Kinda. Read the RFC for SMTP, 2821 and you'll understand my objection. Here's the important bit, from 4.5.4.1, "Sending Strategy":
In a typical system, the program that composes a message has some method for requesting immediate attention for a new piece of outgoing mail, while mail that cannot be transmitted immediately MUST be queued and periodically retried by the sender. A mail queue entry will include not only the message itself but also the envelope information.
The sender MUST delay retrying a particular destination after one attempt has failed. In general, the retry interval SHOULD be at least 30 minutes; however, more sophisticated and variable strategies will be beneficial when the SMTP client can determine the reason for non-delivery.
In other words, if the network is busy or some other odd hiccup happens, the RFC recommends waiting a minimum of a half an hour (or possibly a lot more) before a retransmit. This is why time sensitive stuff should never be emailed - you could be fired for not showing up for that lunch, and it may not be your fault at all. I personally have seen email messages sit in a queue for as long as 2 days before my recipient receives it.
Writing an e-mail that your audience will understand first time - both in tone and in content - takes considerable effort and skill.
Sure it does.
The unit numbers shouldn't matter from a success standpoint, should they? From Wikipedia:
Businessweek magazine compiled a report[1] that estimates the total cost of components in the "premium" bundle at $525 USD, sans manufacturing costs, meaning that Microsoft is losing money on every Xbox 360 system sold. It should be noted that the strategy of selling a console at a loss or near-loss is common in the console games industry, as console makers can usually expect to make up the loss through game licensing.
The console numbers that MS releases are marketing fluff to get developers hot and happy to write games for the Xbox360. The real numbers that need to be looked at to determine if this thing is a success is in numbers of games sold, and the directly related return on investment selling licensing to cover that loss.
They could sell a billion of them, but if nobody buys any games for them - the platform would financially be an epic failure.
He worked on such dogs as Apple Computer's defunct video card business, 3DO's failed game consoles, a chip startup that screwed up a deal with Nintendo, the never successful WebTV and Microsoft's canceled Ultimate TV satellite TV recorder.
What I want to know is how he keeps getting job offers. Seriously - I haven't had 1/100th this much opportunity in my whole entire life.
How the hell does this guy keep landing these?