I prefer UTM (http://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system). Once you get used to it, it's one HELL of a lot easier to work with. ];)
About five years ago at Oshkosh, Williams International was showing-off a compressor turbine hub assembly for their EJ-2 engine. It was milled from a single piece of metal; hub, compressor blades, everything. One piece.
The problem with being a totalitarian regime is that you can never, ever, let-up on that boot you have grinding-down upon the necks of the people, even if you want to. Because the moment you do let-up, the people will stand up, and the next thing you know, you're hanging from a lamp post by a meat hook.
1) Quickest and easiest: Change the port to something oddball. 2) Slightly harder: Set iptables to only permit SSH sessions from selected domains. 3) Getting geeky: Kill password authentication and force sshd to use certificates only. 4) Advanced: Set iptables to DROP IP addresses after three authentication failures within sixty seconds, for sixty seconds. 5) Paranoid: 2+3. 6) Very paranoid: 2+3+4. 7) Go-get-the-guys-in-the-white-suits paranoid: 1+2+3+4.
#4 is my personal favorite. It only takes about three lines in the iptables settings, and it drives script kiddies crazy when their "leet warez" hang.
Does CIO Vivek Kundra have budget authority over these data centers? If not, then the agencies will do with him what they do with every other "czar:" Flip him the bird and go right back to the way they were doing things before.
When one of our more, ah, "intellectually challenged" personnel call the help desk, the first thing I have my people do is have the employee do a screen capture and send it to the help desk. Email if it's not the problem, print if it is. If the employee just plowed through the message without recording it, our SOP is "Reboot. Give us a call when you have a screen capture for us; otherwise we can't troubleshoot your problem."
Possible programming approach: Have the program itself do the screen capture and email. Package the logs with it.
"Many scientists say that such material, ranging from reports by government agencies to respected research not published in scientific journals, is crucial to seeking a complete picture of the state of climate science."
Not only was that disgusting, the "punishment" is frikkin' SCARY.
That's the NEA for you. I swear you couldn't fire one of their union stiffs even if they showed up with a M249 and chopped to pieces every kid in the school.
I was saddled with a ton of code at one point. It looked like it had been banged-out by the proverbial army of monkeys with typewriters, and they sure as hell didn't write Hamlet. It was pure spaghetti code, written by people who shouldn't have had access to an Etch-a-Sketch, let alone a computer.
I couldn't read it. It was COBOL for Pete's sake, and I couldn't read it. It just didn't make sense. I had to go find several DOZEN of those old IBM flowchart pads and a template, and chart-out every single instruction. Even then it didn't make any sense.
Finally, I took all the flowcharts and spread them out on the main computer room floor, a-la A Beautiful Mind, and go crawling around on them with a big fat red marker. My first break was when I realized roughly 60% of the code was "dead:" it would never, ever be branched to. After striking-out all the dead code, I then wrestled with the file I/O, until I realized that whoever had written it had no concept of a buffer: the code would read a record, get a field, read the same record, get another field, etc.
In the end, I trashed roughly 78% of the code and then re-wrote what was left. One program went from 64 pages to sixteen, then on the re-write went down to four. Yup; FOUR. Run-time for that same program went from sixteen HOURS to 32 MINUTES. Then I re-wrote it again, this time in 4GL, and the four pages became a half-page. THEN I had to go to the Big Boss and tell him that whoever had written the original code had rigged the program to generate falsified fiscal information. Yup; the thing lied right through its teeth. You should have seen the reaction.
Whole thing took about three months, untold amounts of coffee, and three bottles of Maalox. Have fun with your own code.
Slashdot Mirror
Love it! Can I quote you?
]:)
I prefer UTM (http://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system). Once you get used to it, it's one HELL of a lot easier to work with.
];)
A helmet?
About five years ago at Oshkosh, Williams International was showing-off a compressor turbine hub assembly for their EJ-2 engine. It was milled from a single piece of metal; hub, compressor blades, everything. One piece.
A 'helmet.' Pbbbbbttttt. . . .
Oh, I dunno; maybe he showed up to work one day driving a car worth ten times his annual salary?
Just because someone can write code doesn't necessarily mean they're not dumber than a turnip.
All the 'best engineers' left NASA after the Apollo program was canceled by the bean-counting Bozos of Congress.
Nothing's left but third-stringers and bureaucrats. Mostly the latter.
The problem with being a totalitarian regime is that you can never, ever, let-up on that boot you have grinding-down upon the necks of the people, even if you want to.
Because the moment you do let-up, the people will stand up, and the next thing you know, you're hanging from a lamp post by a meat hook.
It's becoming increasingly evident that the teaching of History has been discarded in America's centers of "higher" learning.
Orwell was an amateur.
1) Quickest and easiest: Change the port to something oddball.
2) Slightly harder: Set iptables to only permit SSH sessions from selected domains.
3) Getting geeky: Kill password authentication and force sshd to use certificates only.
4) Advanced: Set iptables to DROP IP addresses after three authentication failures within sixty seconds, for sixty seconds.
5) Paranoid: 2+3.
6) Very paranoid: 2+3+4.
7) Go-get-the-guys-in-the-white-suits paranoid: 1+2+3+4.
#4 is my personal favorite. It only takes about three lines in the iptables settings, and it drives script kiddies crazy when their "leet warez" hang.
". . . . the names of 57 patent violations that are in the Linux kernel at present."
~The Manchurian Candidate, the remake, starring Steve Ballmer.
"How messed up is the US when we have to take cues on privacy laws from, of all people, the Germans?"
Actually, the Germans, "of all people," have the advantage of knowing precisely just how bad things can get.
Should I take it that baguettes are now persona non grata in the LHC cafeteria?
....Time to short the stock.
....That's the only question of interest.
Puh-leeze. You get more radiation, of the ionizing type, from standing in the sun for fifteen minutes.
.....Bill-yuns and bill-yuns of itty-bitty buttons, all alike.
Does CIO Vivek Kundra have budget authority over these data centers? If not, then the agencies will do with him what they do with every other "czar:" Flip him the bird and go right back to the way they were doing things before.
'Nuff said.
When one of our more, ah, "intellectually challenged" personnel call the help desk, the first thing I have my people do is have the employee do a screen capture and send it to the help desk. Email if it's not the problem, print if it is.
If the employee just plowed through the message without recording it, our SOP is "Reboot. Give us a call when you have a screen capture for us; otherwise we can't troubleshoot your problem."
Possible programming approach: Have the program itself do the screen capture and email. Package the logs with it.
"Many scientists say that such material, ranging from reports by government agencies to respected research not published in scientific journals, is crucial to seeking a complete picture of the state of climate science."
Or, to support a predetermined conclusion.
'Nuff said.
'Nuff said.
Hello! We're talking about a Microsoft rep here!
Just assume every third sentence that comes out of a MS rep's mouth is a flat-out lie, and rest assured all your cognitive dissonance will go away.
Not only was that disgusting, the "punishment" is frikkin' SCARY.
That's the NEA for you. I swear you couldn't fire one of their union stiffs even if they showed up with a M249 and chopped to pieces every kid in the school.
....wired to a serial port. Worked fine.
. . . the new 'star?'
Used to be, when foundering companies relabeled themselves, the word 'star' was invariably in the new name somewhere.
];)
I was saddled with a ton of code at one point. It looked like it had been banged-out by the proverbial army of monkeys with typewriters, and they sure as hell didn't write Hamlet. It was pure spaghetti code, written by people who shouldn't have had access to an Etch-a-Sketch, let alone a computer.
I couldn't read it. It was COBOL for Pete's sake, and I couldn't read it. It just didn't make sense. I had to go find several DOZEN of those old IBM flowchart pads and a template, and chart-out every single instruction. Even then it didn't make any sense.
Finally, I took all the flowcharts and spread them out on the main computer room floor, a-la A Beautiful Mind, and go crawling around on them with a big fat red marker. My first break was when I realized roughly 60% of the code was "dead:" it would never, ever be branched to. After striking-out all the dead code, I then wrestled with the file I/O, until I realized that whoever had written it had no concept of a buffer: the code would read a record, get a field, read the same record, get another field, etc.
In the end, I trashed roughly 78% of the code and then re-wrote what was left. One program went from 64 pages to sixteen, then on the re-write went down to four. Yup; FOUR. Run-time for that same program went from sixteen HOURS to 32 MINUTES. Then I re-wrote it again, this time in 4GL, and the four pages became a half-page. THEN I had to go to the Big Boss and tell him that whoever had written the original code had rigged the program to generate falsified fiscal information. Yup; the thing lied right through its teeth. You should have seen the reaction.
Whole thing took about three months, untold amounts of coffee, and three bottles of Maalox. Have fun with your own code.
You punish them for getting caught. Unless you're into Theology, that's just the way the world works.
Just what is your point, if any?