I went through a very similar situation about 6 years ago. A small privately owned company handed me an employment contract with several strange clauses in it. The ony I objected to was that any work I do on or off company time could be billed by the company. Since I do volunteer work for various churches, I didn't want them to jump in and bill for my time.
I basicly went to the owner and said "I can't sign this." and explained why. The funny thing was he hadn't even read it himself. He got a boilerplate contract from his lawyer and just passed it on. So he handed it to me and said "OK, rewrite it." I did, on my own. I only weakened the clauses I didn't like and passed it back. If I had really torn it apart, they probably wouldn't have liked it. I did eventually sign my new version, and it worked out fairly well. They didn't even hold me to some of the conditions in it when I left. It was all pretty friendly.
Measure the employer as much as the contract. It's not always possible to gauge them if you don't know them well, but if they work with you in the beginning, it can tell you a lot about how they will react in the end.
It's Reigel in the lead with his giant Mars robot pounding up the ridge behind the new Martian base. Quark takes over on the descent as they enter the power station. He tries to take a sortcut through the archway. Ohhh, that's gotta hurt. He's burried in an avalanch of loose bolders. Tyroid comes up from behind as they move out to the volcanic plains. He powers up and zooms into the lead. Now into the quary and the racers split. Reigel takes the center road, while Zeek takes the low road to the right and Doc slows into the shortcut on the left. They all burst out into the shuttle crash site. Zeek takes a pit stop while Reigel rushes on. Tyroid hits a bump and flies out of control. Reigel enters the abandoned Martian base first, but is overtaken again at the lava jump. Doc is first out of the valley, and takes the sharp turn onto the bridge. It's Doc and Reigel. It's Reigel and Doc. Doc hits the Brick Boost and inches out in front at the lap.
Bill Gates has a private project (Corbis, not affiliated with MS) growing to amass a large collection of photographs. It already does a good business of finding and licensing photos for almost any use. They could be trying to get more for the collection, or to join up in an IP pipeline to benefit both companies.
I wouldn't say "Do Nothing" was an appropriate response, but maybe alter the type of action to take. Rather than attack the problem in terms of prevention (like the Tokyo accord), we could act in terms of preparedness.
By making lots of good measurements of yearly changes of averages in lots of areas, we could make realistic estimates of how regions are likely to change over time. With that, we could make preparations to add food production in new promising areas before the old ones completely dry up. It's planning ahead.
Of course, that means measuring lots of little things like average tempratures, rainfall, glacial melt, sea level, and other things. And then we try to combine it all together in a global model to understant overall effect, and local variation better. In the end, we'd be better able to predict new usefull land for farming, and warn of old land becomming less usefull.
But somehow, that sounds a lot like what the original article was doing, doesn't it. It was indicating climate changes, and estimating global and local effects. Wouldn't you know it, but they are already doing it, planning ahead. Maybe it's not all useless scare tactics after all.
Any good admin knows the most secure system is one that is listening on as few ports as possible.
I would alter that to say responds on as few ports as possible. You can have ports not repsond to things that happen on them. If a port simply records what comes in but never sends any response, then it is no different than a closed port. You're not going to break into a port that does not respond. At best, you might DOS it by taking advantage of internal bugs by sending it a specific pattern of activity.
Single port knocking sequence is a good idea though. You could send it a pattern of IP packets with different protocol headers or some such to wake it up. That's what I thought when I first saw the title. Timing based sequences would not work well, as they would be at the mercy of transmission delays.
Either way, you might be at the mercy of ISP level port or protocol filtering. Better check those out first.
Got it memorized, along woth most of the others in the collection. Kids.
I worked up an alternate wording once that included "Four singing Bugs say YEAH, YEAH, YEAH!". It was mostly pop music based, Beatles and others. Too bad I forgot most of it.
Well, with nano-accuracy and a span of 12 inches, what's the resolution there? The markings on that ruler would have to be in 12 digit numbers at least. If it moves, just take the high and low and subtract. Finally, a good use for 64 bit math.
There is no law of nature that says change is going to be detrimental.
It's not a natural law, it's a political, financial and resource law.
Right now, we have a fairly complex structure of food production needed to keep 6+ billion humans alive. This includes a lot of land in specific places set aside for crops and livestock. If the weather patterns change, earth as a whole will likely still be habitable for humans in general, but any given piece of land may not be suitable for food production. If the current crop lands go bad, and some other land, a thousand miles away suddenly becomes much better for that same crop, then you have to move the whole production machine over to the new location.
This doesn't even account for fights over property rights, cost liabilities, and what to eat during the time it takes to move. A lot of current companies/countries will lose power/influence, and a lot of other landowners, and other countries, suddenly find themselves in control of valuable resources that weren't valuable before. It will, for a while at least, be even more politically and economically destabalizing than the constant bickering over oil is now.
THAT is what the alarmist are talking about, and that is what all the anti-alarmist seem to not understand.
I was driving on the highway (early 90's) and there was a Fiero ahead of me. Sudeenly a piston went flying straight up through the trunk (rear engine) and blew the engine lid open. The car coasted over off the road and was belching smoke. That was a mix of funny and scary. I wonder where that piston landed?
You can take a good look at the terrain on this 3D fly over. You can also control the path and view angles. Give it a try. It's pretty cool.
marsquestonline
There are also other Mars terrain flyovers, and current large pan and zoom pics from Spirit and Opportunity.
Most arguments for case insensitivity are that it is easier or less error prone. If you can't handle getting the case of a name correct, you almost certainly don't have the ability to manage checking parameters and states, or generally doing any of the work involved in writing quality software.
Now hold on there. You're trying to drive way too much assumption through that one. There is no way to tie programmer ability on any level to the issue of case beyond style. Get over it.
A lot of the discussion seems to surround the issue if style and/or readibility. If the compiler is case insensitive, then even if the programmer misses the case, the compiler will pick it up anyway. Certainly the programmer should be consistant, but its not an error. The program won't fail. It's style. It's right up there with the differences over how to arrange your braces. Would you be offended if someone said your style of arranging braces meant you were less capable?
And how about helping someone through something on the phone?
"OK, Now look for foobar. Yes. Foobar. Capital Foo capitol Bar. Yes. No. capital eff, lower oh, lower oh, capitol bee, lower ah, lower arr. Right. No, no space. All together eff oh oh bee ah ar. Right. No. Capitol eff lower oh lower oh, no space, capitol bee.... Aww F**K it!"
I've been programming for 20 years, 15 professionally. I've used plenty of case insensitive languages. It's no killer. I mostly did everything in one case and just went on. I didn't see a need to add my own complexity over what the compiler already enforces. The idea of using some mixed case naming scheme didn't even occur to me or others around me. The compiler didn't care, why should we? It wasn't until I started running into case sensitive languages that I even thought about it. And then, I just kept on using all lower case as if nothing had changed.
If you are already used to case-sensitive languages, then a case-insensitve language may be hard to get used to. But the other way around is easy. It all depends on what side you are looking from.
In this context, "customer" is a fairly vague term. It could be an IS manager hiring you on contract. It could be a project that already has a code base and you are just adding functionality. It could be the customer already has a large installed client base and "your favorite language" doesn't fit in very well. And in my experience, the customer often knows more than you think. They don't always tell you up front (that's a whole different problem) but they have good reasons for what they want.
Their are planty of cases where the programmer simply doesn't have the choice of language or tool to use. You take what they give you and make the best of it. If you can't do it, then they'll get someone else who will. Then what has your language snobery gotten you?
What I really want to see is a rover running up the Face on Mars.
Would you settle for being able to fly your own private spaceship back and forth over the face on mars? If so, go here:
www.marsquestonline.org. 3D pilotable Mars flyovers of many famous sites.
That's the most of it. The other type is "metamorphic" which is either of the other two types (ignious or sedimentary) that has been heated and squeased until it changes structure or chemistry. Metamorphic can be created with or without water, so is not a solid indicator by itself.
Olivine is one of the darkest pure volcanic minerals, found is deep core volcanos like Hawaii and Iceland. (as opposed to granit/mica from subduction zones.) So not only does olivine indicate that it formed and remained in a dry area, but also came from a "dry" volcano.
What you saw was on PBS, NOVA: Mars dead or alive. The home page is here, and there's a link that claims you can watch the whole show here.
Of course the show is 50 minutes or so, and the animation you want is in the middle. I taped it when it was broadcast, and I do like the scene you are describing.
More Mars info here. It includes some nice 3D imaging, large zoom and pans of the latest rover images, and some nice 3D pilotable flyovers of several sites, including Olympus Mons.
It has all the latest Mars Rover info as well, and a direct link to JPL for the latest and greatest pictures and info.
www.marsquestonline.org Go hit it. It's worth a look around.
How did SCO get a copy of "IBM AIX source code, an old version labeled MERCED/9922A_43NIA"?
A few years back, when Intel was first spouting off about Itanium, IBM and SCO were working togethere on a next-generation Unix project targeted at Itanium. That project was called "MERCED". That's most likely where that code came from.
Right. Because building cameras, military aircraft, and nuclear subs takes presidence over essential elements of human life, namely food and clothes. And that isn't backwards. Sure....
Does that apply to the US too?
(Sorry, couldn't help myself. *waves* Hi.)
Slashdot Mirror
I basicly went to the owner and said "I can't sign this." and explained why. The funny thing was he hadn't even read it himself. He got a boilerplate contract from his lawyer and just passed it on. So he handed it to me and said "OK, rewrite it." I did, on my own. I only weakened the clauses I didn't like and passed it back. If I had really torn it apart, they probably wouldn't have liked it. I did eventually sign my new version, and it worked out fairly well. They didn't even hold me to some of the conditions in it when I left. It was all pretty friendly.
Measure the employer as much as the contract. It's not always possible to gauge them if you don't know them well, but if they work with you in the beginning, it can tell you a lot about how they will react in the end.
It's Reigel in the lead with his giant Mars robot pounding up the ridge behind the new Martian base. Quark takes over on the descent as they enter the power station. He tries to take a sortcut through the archway. Ohhh, that's gotta hurt. He's burried in an avalanch of loose bolders. Tyroid comes up from behind as they move out to the volcanic plains. He powers up and zooms into the lead. Now into the quary and the racers split. Reigel takes the center road, while Zeek takes the low road to the right and Doc slows into the shortcut on the left. They all burst out into the shuttle crash site. Zeek takes a pit stop while Reigel rushes on. Tyroid hits a bump and flies out of control. Reigel enters the abandoned Martian base first, but is overtaken again at the lava jump. Doc is first out of the valley, and takes the sharp turn onto the bridge. It's Doc and Reigel. It's Reigel and Doc. Doc hits the Brick Boost and inches out in front at the lap.
Bill Gates has a private project (Corbis, not affiliated with MS) growing to amass a large collection of photographs. It already does a good business of finding and licensing photos for almost any use. They could be trying to get more for the collection, or to join up in an IP pipeline to benefit both companies.
By making lots of good measurements of yearly changes of averages in lots of areas, we could make realistic estimates of how regions are likely to change over time. With that, we could make preparations to add food production in new promising areas before the old ones completely dry up. It's planning ahead.
Of course, that means measuring lots of little things like average tempratures, rainfall, glacial melt, sea level, and other things. And then we try to combine it all together in a global model to understant overall effect, and local variation better. In the end, we'd be better able to predict new usefull land for farming, and warn of old land becomming less usefull.
But somehow, that sounds a lot like what the original article was doing, doesn't it. It was indicating climate changes, and estimating global and local effects. Wouldn't you know it, but they are already doing it, planning ahead. Maybe it's not all useless scare tactics after all.
I would alter that to say responds on as few ports as possible. You can have ports not repsond to things that happen on them. If a port simply records what comes in but never sends any response, then it is no different than a closed port. You're not going to break into a port that does not respond. At best, you might DOS it by taking advantage of internal bugs by sending it a specific pattern of activity.
Single port knocking sequence is a good idea though. You could send it a pattern of IP packets with different protocol headers or some such to wake it up. That's what I thought when I first saw the title. Timing based sequences would not work well, as they would be at the mercy of transmission delays.
Either way, you might be at the mercy of ISP level port or protocol filtering. Better check those out first.
I worked up an alternate wording once that included "Four singing Bugs say YEAH, YEAH, YEAH!". It was mostly pop music based, Beatles and others. Too bad I forgot most of it.
...
if a=4 print "Three singing pigs say LA LA AL!"
Well, with nano-accuracy and a span of 12 inches, what's the resolution there? The markings on that ruler would have to be in 12 digit numbers at least. If it moves, just take the high and low and subtract. Finally, a good use for 64 bit math.
It's not a natural law, it's a political, financial and resource law.
Right now, we have a fairly complex structure of food production needed to keep 6+ billion humans alive. This includes a lot of land in specific places set aside for crops and livestock. If the weather patterns change, earth as a whole will likely still be habitable for humans in general, but any given piece of land may not be suitable for food production. If the current crop lands go bad, and some other land, a thousand miles away suddenly becomes much better for that same crop, then you have to move the whole production machine over to the new location.
This doesn't even account for fights over property rights, cost liabilities, and what to eat during the time it takes to move. A lot of current companies/countries will lose power/influence, and a lot of other landowners, and other countries, suddenly find themselves in control of valuable resources that weren't valuable before. It will, for a while at least, be even more politically and economically destabalizing than the constant bickering over oil is now.
THAT is what the alarmist are talking about, and that is what all the anti-alarmist seem to not understand.
Don't let on, but it might not have been his wife....
I was driving on the highway (early 90's) and there was a Fiero ahead of me. Sudeenly a piston went flying straight up through the trunk (rear engine) and blew the engine lid open. The car coasted over off the road and was belching smoke. That was a mix of funny and scary. I wonder where that piston landed?
marsquestonline
There are also other Mars terrain flyovers, and current large pan and zoom pics from Spirit and Opportunity.
Now hold on there. You're trying to drive way too much assumption through that one. There is no way to tie programmer ability on any level to the issue of case beyond style. Get over it.
A lot of the discussion seems to surround the issue if style and/or readibility. If the compiler is case insensitive, then even if the programmer misses the case, the compiler will pick it up anyway. Certainly the programmer should be consistant, but its not an error. The program won't fail. It's style. It's right up there with the differences over how to arrange your braces. Would you be offended if someone said your style of arranging braces meant you were less capable?
And how about helping someone through something on the phone?
"OK, Now look for foobar. Yes. Foobar. Capital Foo capitol Bar. Yes. No. capital eff, lower oh, lower oh, capitol bee, lower ah, lower arr. Right. No, no space. All together eff oh oh bee ah ar. Right. No. Capitol eff lower oh lower oh, no space, capitol bee.... Aww F**K it!"
I've been programming for 20 years, 15 professionally. I've used plenty of case insensitive languages. It's no killer. I mostly did everything in one case and just went on. I didn't see a need to add my own complexity over what the compiler already enforces. The idea of using some mixed case naming scheme didn't even occur to me or others around me. The compiler didn't care, why should we? It wasn't until I started running into case sensitive languages that I even thought about it. And then, I just kept on using all lower case as if nothing had changed.
If you are already used to case-sensitive languages, then a case-insensitve language may be hard to get used to. But the other way around is easy. It all depends on what side you are looking from.
Their are planty of cases where the programmer simply doesn't have the choice of language or tool to use. You take what they give you and make the best of it. If you can't do it, then they'll get someone else who will. Then what has your language snobery gotten you?
Would you settle for being able to fly your own private spaceship back and forth over the face on mars? If so, go here: www.marsquestonline.org. 3D pilotable Mars flyovers of many famous sites.
Olivine is one of the darkest pure volcanic minerals, found is deep core volcanos like Hawaii and Iceland. (as opposed to granit/mica from subduction zones.) So not only does olivine indicate that it formed and remained in a dry area, but also came from a "dry" volcano.
Of course the show is 50 minutes or so, and the animation you want is in the middle. I taped it when it was broadcast, and I do like the scene you are describing.
Hope that helps.
It has all the latest Mars Rover info as well, and a direct link to JPL for the latest and greatest pictures and info. www.marsquestonline.org
Go hit it. It's worth a look around.
Just because it was mentioned in the article doesn't mean he couldn't vote for it. No need to be rude.
So how many of us would have made it all the way through the boss levels if we actually had to be able to lift the BFG9000?
marsquestonline
Warning: Flash required.
A few years back, when Intel was first spouting off about Itanium, IBM and SCO were working togethere on a next-generation Unix project targeted at Itanium. That project was called "MERCED". That's most likely where that code came from.
Legal fund: We have this much money to defend you with. I hope it's enough.
Indemnification: We take full responsibility. Any legal action will come completely though us, no matter the cost.
You can see why not very many companies do it.
Does that apply to the US too?
(Sorry, couldn't help myself. *waves* Hi.)
Lego Spirit Rover