Here's one I heard from my co-workers about one gag they did many years ago.
The office building had two long rooms of cubicles on either side of a hallway. One day, one room took a bunch of people (close to everyone who worked there, about 30-40), a hat was filled with the various extensions from across the hall, each picked one, and everyone dialed the last digit at the precise same instant. The clatter of simultaneous rings from across the hall (I'm told) was hilarious. They all hung up after one ring.
Of course, this from the days of older-style desk phones that use an actual bell as the ringer. This may not work quite so well today, our phones are now digital and have caller ID. Then again, I'm surprised it worked back whenever they did that, not blowing a circuit from all the calls being made at once.
well that was fast. the only thing that i can recall having been passed in faster fashion were the House & Sentate approvals required to purchase the land for and the construction of the Pentagon. Took something like less than a month for the War Dept to go from concept to groundbreaking ceremony. Then another couple months for actual work to start in the first wedge.
one of the articles i've read on this said that the judge said the FTC overstepped it's authority. Several members of congress responded with something like "No, we gave them that authority when we drafted and enacted laws permitting the creation of the DNC"
I can understand having a clock in some environments, but I dont see the need for a clock in the typical Office Space style workplaces. My own timesheet doesn't even ask for times, just the total hours worked for each day and for what contract. My supervisor signs the sheet at the end of the week, and I feel it's more than sufficient. If someone feels that there's some tampering or other shenanigans going on, there are ways to figure that out. Like when they're work doesn't get done, or keeping tabs on when they actually show up and leave the office.
Linux in general is more popular than this project. That popularity gives it more eyes to keep watch on it, and shorter turnarounds when problems are found.
As for this project (CIPE), I personally have never heard of it. Indeed, neither has the poster from that mailing list: A friend of mine recently pointed me at CIPE, a Linux VPN tool that he claimed was widely used but that no-one else I know seems to have heard of.
Murphy's law originally stated that if something can go wrong, at some point it will, therefore make it such that the somthing can't go wrong. In other words, idiot-proofing is required when building something.
For example, PS2 connections for keyboards and mice are keyed to prevent being plugged in the wrong way.
GUI developers (especially KDE and GNOME developers!!!) should take notes on things like this.
how much you wanna bet that the RIAA, upon getting a target's address from their ISP, looked up that address on mapquest and used the aerial photos to determine what type of neighborhood it was?
big mansion, move on to next address. highly concentrated block of row-homes, off to court with suit in hand.
Assume NASA did attempt to evaluate the damage and it revealed the Columbia to be a death trap. Yeah, there will be media coverage had it become necessary to send up a repair crew or something.
But there would be an Apollo 13 type effort. Atlantis could go up with a minimal crew and pick up the Columbia crew. Maybe do it in two flights. Leave the Columbia in space until repair becomes possible. Not possible? They'd find a way.
Or, engineer a solution on the ground and figure out a way to get that solution up into space and istalled. Again, an Atlantis crew would head up with the necessary materials and perhaps be the ones to do the repair job. Sounds like the Hubble, doesnt it? Also impossible? They'd find a way.
Engineers are quite capable of great things, and you seem to be underestimating the potential of great thinkers. When JFK made his "before this decade is out" challenge, everyone at NASA thought "No way! You've got to be kidding." But then the people who would do it got thinking of ways they could and they came through.
Homer: So what do you call this stuff? Barney: A double tall mocha latte. Homer: It's not bad. (quietly spikes his drink) Barney: Well, it ain't beer, but at least I got that monkey off my back. (quickly gulps down four cups, then burps)
(Cut to Moe) Moe: Heh, heh, nobody gets away from Moe. Nobody.
that is indeed still the case today. This past spring I was a TA for a freshman programming course, and was instructed to deduct points for those who didnt follow such practices -- pi, hours/day, minutes/hour, etc. On exams, the prof would write "-5 - use of magic numbers."
oh, and we laughed long and hard at the guy who put down:
... didnt ask any questions about the BSD involvement. almost like she didnt know about bruce peren's findings. yet, the day before (8/20) she published an article with peren's assertions. question becomes: when did this interview take place?
reading that reminded me of somehting Ken Lay's (Enron CEO or something) wife said. She said they've had to sell two or three of their (multi-million dollar) houses as a result of Enron's scandal, in hopes of sympathies or something. Business2 magazine (in their 2001's 101 worst moments) picked up on the fact the Lay's still had several other expensive homes at their disposal.
Microsoft would find out about it. Thousands (millions?) of machines would suddenly stop working, making news headlines similar to Blaster. Hence, MS would be forced into doing something, like a patch to rollback an earlier patch. It may also get regular people asking if anything else is out there if it starts happening a lot.
That's one of the major problems. Windows has had an auto-update notifier for some years now. It checks windowsupdate regularly, and if a new critical patch is available, a dialog box asks if you want to download it. Most people have optioned to not do so.
IIRC, WinXP gives the option to make it download a critical patch without asking, but that's turned off by default.
Slashdot Mirror
dont forget Oriole Park at Camden Yards, a great place to watch a baseball game. Unless you're a fan of the 20-games-under-.500 Orioles.
Here's one I heard from my co-workers about one gag they did many years ago.
The office building had two long rooms of cubicles on either side of a hallway. One day, one room took a bunch of people (close to everyone who worked there, about 30-40), a hat was filled with the various extensions from across the hall, each picked one, and everyone dialed the last digit at the precise same instant. The clatter of simultaneous rings from across the hall (I'm told) was hilarious. They all hung up after one ring.
Of course, this from the days of older-style desk phones that use an actual bell as the ringer. This may not work quite so well today, our phones are now digital and have caller ID. Then again, I'm surprised it worked back whenever they did that, not blowing a circuit from all the calls being made at once.
well that was fast. the only thing that i can recall having been passed in faster fashion were the House & Sentate approvals required to purchase the land for and the construction of the Pentagon. Took something like less than a month for the War Dept to go from concept to groundbreaking ceremony. Then another couple months for actual work to start in the first wedge.
one of the articles i've read on this said that the judge said the FTC overstepped it's authority. Several members of congress responded with something like "No, we gave them that authority when we drafted and enacted laws permitting the creation of the DNC"
oh that's just too easy. watch, I'll do it with my 56K dialup:
(&#^@%}{:> NO CARRIER
Why melt your modem. Ctrl-C...Ctrl-V:
:-)
Bah. REAL men retype the article character by character.
Rent-a-Cop security guard: "Wow! My horoscope was right!" Looks at piece of paper, "You will face challenges today."
(Episode CABF06)
before some gammar nazi points it out, yes i made a goof. That last sentence should be "Like when their work doesn't get done..."
Do employers trust employees anymore?
I can understand having a clock in some environments, but I dont see the need for a clock in the typical Office Space style workplaces. My own timesheet doesn't even ask for times, just the total hours worked for each day and for what contract. My supervisor signs the sheet at the end of the week, and I feel it's more than sufficient. If someone feels that there's some tampering or other shenanigans going on, there are ways to figure that out. Like when they're work doesn't get done, or keeping tabs on when they actually show up and leave the office.
Linux in general is more popular than this project. That popularity gives it more eyes to keep watch on it, and shorter turnarounds when problems are found.
As for this project (CIPE), I personally have never heard of it. Indeed, neither has the poster from that mailing list: A friend of mine recently pointed me at CIPE, a Linux VPN tool that he claimed was widely used but that no-one else I know seems to have heard of.
uh, yes they are. (oh how i love google image search)
Murphy's law originally stated that if something can go wrong, at some point it will, therefore make it such that the somthing can't go wrong. In other words, idiot-proofing is required when building something.
For example, PS2 connections for keyboards and mice are keyed to prevent being plugged in the wrong way.
GUI developers (especially KDE and GNOME developers!!!) should take notes on things like this.
-conspiracy theory hat on-
how much you wanna bet that the RIAA, upon getting a target's address from their ISP, looked up that address on mapquest and used the aerial photos to determine what type of neighborhood it was?
big mansion, move on to next address. highly concentrated block of row-homes, off to court with suit in hand.
-conspriacy hat off-
i'd at least expect better spelling than CmdrTaco's.
well than again this is fox were talking about.......
It gets better....
CmdrTaco posted both of them! That's worse than the usual timothy and michael not reading each other's post and duplicating within days of each other!
For a daily dose of those needing a clue-stick:
http://www.computerworld.com/sharky
Bookmark it people! Put it on your daily reading list! A new story every day!
No, I beg to differ.
Assume NASA did attempt to evaluate the damage and it revealed the Columbia to be a death trap. Yeah, there will be media coverage had it become necessary to send up a repair crew or something.
But there would be an Apollo 13 type effort. Atlantis could go up with a minimal crew and pick up the Columbia crew. Maybe do it in two flights. Leave the Columbia in space until repair becomes possible. Not possible? They'd find a way.
Or, engineer a solution on the ground and figure out a way to get that solution up into space and istalled. Again, an Atlantis crew would head up with the necessary materials and perhaps be the ones to do the repair job. Sounds like the Hubble, doesnt it? Also impossible? They'd find a way.
Engineers are quite capable of great things, and you seem to be underestimating the potential of great thinkers. When JFK made his "before this decade is out" challenge, everyone at NASA thought "No way! You've got to be kidding." But then the people who would do it got thinking of ways they could and they came through.
Homer: So what do you call this stuff?
Barney: A double tall mocha latte.
Homer: It's not bad. (quietly spikes his drink)
Barney: Well, it ain't beer, but at least I got that monkey off my back. (quickly gulps down four cups, then burps)
(Cut to Moe)
Moe: Heh, heh, nobody gets away from Moe. Nobody.
oh, and we laughed long and hard at the guy who put down:
... didnt ask any questions about the BSD involvement. almost like she didnt know about bruce peren's findings. yet, the day before (8/20) she published an article with peren's assertions. question becomes: when did this interview take place?
honestly - if SCO had someone like the parent poster, he'd be gone and in would be someone else, repeating itself until a Yes man is found.
reading that reminded me of somehting Ken Lay's (Enron CEO or something) wife said. She said they've had to sell two or three of their (multi-million dollar) houses as a result of Enron's scandal, in hopes of sympathies or something. Business2 magazine (in their 2001's 101 worst moments) picked up on the fact the Lay's still had several other expensive homes at their disposal.
Microsoft would find out about it. Thousands (millions?) of machines would suddenly stop working, making news headlines similar to Blaster. Hence, MS would be forced into doing something, like a patch to rollback an earlier patch. It may also get regular people asking if anything else is out there if it starts happening a lot.
Yikes! Can I at least press 'Ok' first?
That's one of the major problems. Windows has had an auto-update notifier for some years now. It checks windowsupdate regularly, and if a new critical patch is available, a dialog box asks if you want to download it. Most people have optioned to not do so.
IIRC, WinXP gives the option to make it download a critical patch without asking, but that's turned off by default.
but they're still bluring out other parts
http://news.com.com/2100-1016_3-5065286.html