Actually, they tasered the tank and it shorted the taser out. The cop was referring to that when he said he'd never seen anything like that before. Those things almost never short out.
I also have a funny story. I visited Santa Fe a year ago and stopped to look at the merchandise of a man selling Indian jewelry on the main square downtown. One of the things he was selling was bolo ties.
Making conversation, I said "Isaac Asimov was known to have worn a bolo tie."
And he replied "Well tell him to get down here and buy some ties from me."
Not currently gay, but in the grand scheme of things I am MORE afraid of bullets than I am afraid of other men's hairy asses. Plus with the way television is going it could be a nice career move.
Best solution: Teach your kids to cite primary sources, not encyclopedia articles.
Not as good solution: save the article into a separate web page. Reports in the 21st century should have all the references turned into hyperlinks anyway. Why not just include the full text of the article accessible through a click?
Terrible solution: print the article. Paperclip it to the report.
There must be some trick to reading logs that I haven't figured out yet. For example, I just read my log and it said that the climate is going to be long, brown, smelly, squishy, and somewhat moist. Followed by a localized cyclonic oceanic disturbance, and a short trip down a narrow pipe.
People shouldn't be used to make telemarketing calls, or used to work at Walmart. This is a waste of a valuable person. Even if that person is wearing a mullet. We'd all be better off if they just moved to the places where the jobs are (cue Sam Kineson here).
You're right on. It's the same as the broken windows fallacy. If you went around breaking windows, you'd employ a lot of people, making windows, fixing windows, sweeping up broken glass. But, would we be any further ahead? Of course not. These telemarketers are a boil on the ass of society. They are leeching, not contributing.
OK, forget about him signing it. Just hand him the piece of paper that says if you hack our systems, we'll send you to jail and we have the will to do it. If you give away our secrets, we'll nail your ass to the wall.
Lots of people here are saying that you should kiss this guy's ass. I see no such need to do that. Tell him exactly what you will do to him if he screws you. Make him think twice about it.
Lawyers and insurance. At his exit interview make him sign another piece of paper asking him if he's aware that breaching security is a crime, that he has a responsibility to protect your secrets, and that you can and will send him to jail if he betrays that trust.
Nothing else you can do, except do a code review of all the systems he had access to.
What is your system load? If it's less than 1, you've got processor power to spare. If it's more than one, you could add more processors IF you think that site response is too slow.
What is the throughput to your disks? Actually benchmark this with vmstat or something like that. If that shows that your disks are constantly maxed you could get more servers to spread the disk activity around, or you could build a faster disk subsystem if you've got a centralized database. Smart architecting helps too. Don't run the database on the same processors that run scripts and serve pages. Use the database load handling features to improve that specific part of the site. See what pages you can generate statically - I doubt that every single page on a site needs to be from the database.
If the restroom is occupied, you should check Ronald Reagan's grave. There are often long lines for the urinals, but you never know.
It's not bullshit, it's the truth. I'm Charlton Heston, I'm dead, and I would not lie to you.
Actually, they tasered the tank and it shorted the taser out. The cop was referring to that when he said he'd never seen anything like that before. Those things almost never short out.
I'm dead! I'm dead! And I still got my gunz you dirty apes! Cold dead fingers in your EYE!
I also have a funny story. I visited Santa Fe a year ago and stopped to look at the merchandise of a man selling Indian jewelry on the main square downtown. One of the things he was selling was bolo ties.
Making conversation, I said "Isaac Asimov was known to have worn a bolo tie."
And he replied "Well tell him to get down here and buy some ties from me."
Not currently gay, but in the grand scheme of things I am MORE afraid of bullets than I am afraid of other men's hairy asses. Plus with the way television is going it could be a nice career move.
Being gay is very handy too. Don't ask don't tell? Well --- if they are shooting at me, I'm definitely telling.
If you run GNU Linux and want to get off the grid, this might be your solution. NWFW. Ok, it's a little SFW, but it might be embarassing if your boss walks up.
Any tree that would voluntarily take part in Novel documentation deserved to die.
Best solution: Teach your kids to cite primary sources, not encyclopedia articles.
Not as good solution: save the article into a separate web page. Reports in the 21st century should have all the references turned into hyperlinks anyway. Why not just include the full text of the article accessible through a click?
Terrible solution: print the article. Paperclip it to the report.
Sort of like a Bill Gates cream pie!
Anything that requires me to use all 10 fingers to calculate is definitely fancy.
You're damned right I have a lot of accounts. You can't find them all.
There must be some trick to reading logs that I haven't figured out yet. For example, I just read my log and it said that the climate is going to be long, brown, smelly, squishy, and somewhat moist. Followed by a localized cyclonic oceanic disturbance, and a short trip down a narrow pipe.
Did someone say monkeys? I hate monkeys.
Nope, try 1984 when an astronaut using the MMU orbited all by his lonesome.
Wow, judging by that link you weren't kidding when you said that you were gobbling a lot more cock lately.
Ten years ago I was running Linux on a 3 MIPS 80386SX, running at 20 Mhz.
It had 30 megs of disk set aside (65 meg disk total) for Linux. It had 4 megs of RAM.
The modem was 2400 baud. I had a serial mouse, hooked up to a 9 pin serial port. The monitor could do 640x480, and my video card was VGA only.
But it ran Linux, and it was glorious!
And, as Pee Wee Herman showed, you can't wank in a public theater, but you can wank at home.
People shouldn't be used to make telemarketing calls, or used
to work at Walmart. This is a waste of a valuable person. Even if that
person is wearing a mullet. We'd all be better off if they
just moved to the places where the jobs are (cue Sam Kineson here).
You're right on. It's the same as the broken windows fallacy. If you went around breaking windows, you'd employ a lot of people, making windows, fixing windows, sweeping up broken glass. But, would we be any further ahead? Of course not. These telemarketers are a boil on the ass of society. They are leeching, not contributing.
(from the article) When people think of server UNIX, they think of SCO. hhahahahaha. Mod +5 funny.
I usually think of Sun, or HP, or AIX. But not SCO.
OK, forget about him signing it. Just hand him the piece of paper that says if you hack our systems, we'll send you to jail and we have the will to do it. If you give away our secrets, we'll nail your ass to the wall.
Lots of people here are saying that you should kiss this guy's ass. I see no such need to do that. Tell him exactly what you will do to him if he screws you. Make him think twice about it.
Then, if he screws you, take him to court.
Lawyers and insurance. At his exit interview make him sign another piece of paper asking him if he's aware that breaching security is a crime, that he has a responsibility to protect your secrets, and that you can and will send him to jail if he betrays that trust.
Nothing else you can do, except do a code review of all the systems he had access to.
Who cares what everyone else does?
What is your system load? If it's less than 1, you've got processor power to spare. If it's more than one, you could add more processors IF you think that site response is too slow.
What is the throughput to your disks? Actually benchmark this with vmstat or something like that. If that shows that your disks are constantly maxed you could get more servers to spread the disk activity around, or you could build a faster disk subsystem if you've got a centralized database. Smart architecting helps too. Don't run the database on the same processors that run scripts and serve pages. Use the database load handling features to improve that specific part of the site. See what pages you can generate statically - I doubt that every single page on a site needs to be from the database.