Just a note on point A. When asked in a television interview what his first order of business would be when elected Senator Kerry's response was eliminate the Bush tax cuts. For me, not a wealthy man by any means, that is a tax increase and not an insignificant one.
I try to refrain from "me too" posts but I can't help myself. If any changes are on the horizon how does it effect those of us who already have a.org domain? I have some years invested in this by now and though my use of.org may not have been what the founders intended it has become part of my online identity. (I know that doesn't mean much to anyone but me and the people I am in direct contact with.)
I have to wonder how this would effect those of use who already paid our dimes.
Your friends must be looking in the wrong place. I'm still employed just thought I would test the waters to see what else is out there. My experience is with Solaris, Tru64, and linux administration. Just posting my resume got me about 35 responses in the first 4 days. Most of them were of no interest to me but I have decided to interview for 3 of them. All great jobs.
Of course it may well relate to that truism "It's easier to find a job when you already have one."
and it wasn't a.com, but the most amuzing termination experience I had was while working as a salesman for a oil field services company.
I was asked to drive to the office (which I never did since I worked on the road or from home). When I arrived I found the place padlocked and a guy from the bank there to take my company credit cards and car. They wouldn't even give me a lift back to town. They did finally let me use a phone in the office to call a friend for a ride.
We plan, backup, build redundant systems, isolate production from testing and implementation, and still every now and then something happens that makes you realize how young all this technology really is, and that bottlenecks still exist.
I am just coming off a twenty hour day repairing problems in a production system. Both members of a cluster affected (by the clustering software itself of course). In the end we end up hacking out the best fix available on the fly.
Dependability is expensive, and that expense is often hard to justify to economy minded business people. Add to that the fact that even the most secure, stable, and isolated system will eventually break and it is a recipe for some very long days for those of us who answer the pages when it all falls down.
Good thing I enjoy this kind of work. Now its off to a nap then back to the office to listen to a vendor tell me his next release will address the trouble and explain to a few business folks that simply stating a system will be up 24/7 doesn't make it so.
Transferable enough to let you work out the differences without too much trouble. After all the how to is the easy part, it is determining what to do and what not to do that can be the most difficult.
If you have a hammer everything looks like a nail.
If you ask a Canadian everything looks like snow.
Just a note on point A.
When asked in a television interview what his first order of business would be when elected Senator Kerry's response was eliminate the Bush tax cuts.
For me, not a wealthy man by any means, that is a tax increase and not an insignificant one.
Somewhere there must be a serious shortage of tin hats.
I try to refrain from "me too" posts but I can't help myself. If any changes are on the horizon how does it effect those of us who already have a .org domain? I have some years invested in this by now and though my use of .org may not have been what the founders intended it has become part of my online identity. (I know that doesn't mean much to anyone but me and the people I am in direct contact with.)
I have to wonder how this would effect those of use who already paid our dimes.
Your friends must be looking in the wrong place. I'm still employed just thought I would test the waters to see what else is out there. My experience is with Solaris, Tru64, and linux administration. Just posting my resume got me about 35 responses in the first 4 days. Most of them were of no interest to me but I have decided to interview for 3 of them. All great jobs.
Of course it may well relate to that truism "It's easier to find a job when you already have one."
and it wasn't a .com, but the most amuzing termination experience I had was while working as a salesman for a oil field services company.
I was asked to drive to the office (which I never did since I worked on the road or from home). When I arrived I found the place padlocked and a guy from the bank there to take my company credit cards and car. They wouldn't even give me a lift back to town. They did finally let me use a phone in the office to call a friend for a ride.
We plan, backup, build redundant systems, isolate production from testing and implementation, and still every now and then something happens that makes you realize how young all this technology really is, and that bottlenecks still exist.
I am just coming off a twenty hour day repairing problems in a production system. Both members of a cluster affected (by the clustering software itself of course). In the end we end up hacking out the best fix available on the fly.
Dependability is expensive, and that expense is often hard to justify to economy minded business people. Add to that the fact that even the most secure, stable, and isolated system will eventually break and it is a recipe for some very long days for those of us who answer the pages when it all falls down.
Good thing I enjoy this kind of work. Now its off to a nap then back to the office to listen to a vendor tell me his next release will address the trouble and explain to a few business folks that simply stating a system will be up 24/7 doesn't make it so.
Transferable enough to let you work out the differences without too much trouble. After all the how to is the easy part, it is determining what to do and what not to do that can be the most difficult.