Actually, the Range reports a precise liftoff time down to the millisecond, based on first motion of the vehicle. In this case, it was 7:43:44.074 p.m. EDT according to Spaceflight Now.
It might be nice if they had bothered with an official web site that contained any decent, up-to-date information about the mission. The "News" section is basically just the home page with nothing timely, and the latest entry on the "Press Releases" page is four days old.
You're right. Not only that, the border with Canada passes through the approximate middle of the rest of the Great Lakes (except around Isle Royale in Lake Superior, where it cuts much closer to the Canadian shore), so the "border zone" covers much less land there. Ironically, even though the map shows Michigan as being completely within the zone, TFA omits that state in its list.
I find humour in the fact that whenever a Wikipedia editor writes "Truth" in the edit summary, 9 times out of 10 the edit is not actual fact but rather POV, bullshit, or simple vandalism.
I know a couple who endowed a scholarship at their alma mater. They intended it to help promote women in computer science. But because of Title IX the scholarship can't have a gender-based requirement, so it's awarded to someone "whose presence promotes diversity".
Trouble is, it's still stuck using distilled water. I'm waiting for a hydrogen converter that can handle rainwater, or household greywater, or the aforementioned on-board pee tube.
The question you asked was, "Is it best to move on to another company or to stay where you are and try to get ahead there?", so let's ignore all the knee-jerk "all bosses are lobotomized PHBs" responses and assume that you truly want to leverage your experience and talents into a position with increased responsibility, authority, and (one hopes) salary.
The short and generalized answer is, moving on is better than staying put.
The IT worker always suffers under the role of the "man behind the curtain." As in, "Pay no attention to the..." If you're doing your job right, the major problems you're solving are never getting noticed by those who might have been affected by them. You can fight fires all day long every day and no one will know until that one time they smell a little smoke. Even those big projects where you shine and do a great job and bring it in ahead of time and under budget get forgotten the moment the first follow-on issue arises.
Because of this, tooting your own horn at your corrent job probably won't help much. You'll say, "look what I fixed" and hear "but this is broken." You'll say "look what I built" and hear "yes, but what about all this other stuff that needs doing?"
Add to that the inertia of those in positions above you. You didn't say whether they had already hired someone to fill that IT manager position above you. If they did, how long do you think it will be until they move on, or move up, and enable you to take that role?
The moment you're hired, you're pigeonholed into a specific role. Those who see you as just the "lowly IT person" won't be able to see you as a manager, no matter how well you demonstrate your leadership, logistical ability, and business savvy. At best, they might see you as "that awesome IT person" -- and will think of you as irreplaceable in the position you're already in.
Instead, if you move on to someplace else, you have the chance to put your knowledge and experience in the very best light, as you describe them in your résumé and in interviews. ("Spearheaded a project" sounds much better to a prospective hirer than "Sat through numerous interminable meetings before doing it all myself because no one could come to a decision" does to your current boss.) You also get to start with a blank slate with regard to what you might be capable of doing. Every time I've started a new job, I've been hired to do many things that I'd never actually done before.
At my first full-time job I was hired as a programmer and analyst at a university, with plenty of help desk work. Although my influence on decision-making grew somewhat during the time I was there, after several years it was clear that my boss had no inclination to move up or move on. There was nowhere for me to go, so I moved on.
Next, I was hired as a support specialist in a state agency, at a 10% salary boost. I was the team leader for many projects there, but when my boss quit and I had to shoulder most of his responsibilities, rather than promote me into his position they eliminated it. I wound up with all his work and none of his benefits.
I moved on to a privately-owned company and became their senior network admin with another rise in salary. I helped coordinate a major construction project of a new office (and no, I had no prior experience in this) that came in on time and under budget. After that I volunteered for several other big projects that effectively never left the wish-list phase, and wound up doing mostly day-to-day firefighting that never got noticed except in those rare failures. And my manager had been there for years and wasn't going anywhere. So I started looking around again...
One word of caution: when you start looking beyond the walls of your current job, be circumspect and anonymous. At this job, unbeknownst to me, the HR department had a policy of periodically checking the major job boards (Monster.com, etc.) for résumé postings from employees. Those they found were summaril
Only a 75 year old white lady can get away with something like that. If it was a 15 to 25 year old black male, then he would already be in Gitmo...
That comment is ageist, sexist, and racist. Way to hit the trifecta.
If it were possible for a 15-year-old black male to have already had a long career with the Air Force as a registered nurse, and had a husband who has similarly served his country, he'd probably get the same slap on the wrist. Being a military veteran can get you a lot of slack from the cops, many of whom are vets too.
It might. Garmin also uses Navteq maps in its GPS devices -- in fact Navteq is Garmin's most important supplier -- and Garmin's stock price went into the dumper today on the NYSE because of fear that Garmin will have less influence, both in pricing and features, on Navteq when it's owned by Nokia.
IMO, NASA should mothball the Shuttle immediately and put all its effort into developing the Ares system. They would have to re-manifest some crews and hardware aboard Soyuz and Proton rockets for the next few years, but that would allow their current engineering talent to focus exclusively on the new system, avoid the brain drain that Administrator Griffin fears, and save a bunch of money in the process. I bet with focus they could have flight-worthy hardware by 2010.
In 2000 I contributed a chapter to a book on U.S. launch vehicle history. Before I sent my final draft to the editors, I ran it through Turnitin. This I did as a form of self-preservation, because given that the vast portion of my chapter was heavily based on other sources, I wanted to be sure that I had done an adequate job of paraphrasing and attribution. (My scan, by the way, came up clean.)
Now, while I have some concern that a copy of my chapter resides on Turnitin's servers, I am fairly certain that no more than appropriately-sized excerpts will ever be reprinted there, and then only in cases of likely inappropriate borrowing. Moreover, I am happy that it's there, for this reason: it establishes a record of prior existence. No one subject to a Turnitin review will be able to crib from me without proper attribution.
None of this, of course, has prevented a substantial case of plagiarism of my chapter by a contributor to the Thor rocket page on Wikipedia.
Hilarious, his best work since his spoof of "Smells Like Teen Spirit."...but call me an old fart with no awareness of current music, especially hip-hop -- I have no idea what song this is based on.
My desk neighbour has a U-505 submarine sitting on his monitor that he got last year at the Museum of Science and Industry. The mold for it is probably 50 years old and still going strong. (By the way, the new exhibition space for the U-505 is worth a trip to Chicago just to see that.)
If non-flight, space-related deaths are included, one would have to include Charlie Bassett, Elliott See, and C.C. Williams. All three astronauts died in T-38 crashes while in the line of duty for the American space program.
As others have said, most places in the U.S. this wouldn't work, since (1) corporate stores won't do discounts, and (2) only a jerk would negotiate a price at a mom-and-pop store that's already being undercut by the Wal-Mart and Costco down the street. (One exception: those cluttered electronics stores in New York City. Haggle to your heart's content there.) In China, except for higher-end shopping districts, negotiating the price is expected.
A problem with group-buy is this: when negotiating, one should always be prepared to walk away. My wife and I used this move in China several times, and it almost always resulted in an instant price cut. With 500 people, seems like it would be tough to get enough momentum to head for the door. That much mass takes that threat off the table.
Earlier this year, the Washington D.C. Metro held a competition to find a new voice for the subway's automatic announcements. Part of the reason for this was that riders had gotten too familiar with the old voice and had started to ignore the "doors closing" warning.
Seems to me that the coffee room eyes would have to be replaced periodically as well, because as people got used to them they'd start to ignore them.
FTA: The Citizen Lab uses the techniques of spies to secretly deploy software it developed that automatically checks for censored websites inside various countries. Sometimes the lab performs tests remotely, taking control of unprotected computers inside the censoring country without permission. This poses an ethical controversy, but Deibert says it's for the greater good: "We don't worry about that too much." (emphasis added)
I agree with the project's intent, but how does this differ from, say, writing a virus that forces remote computers to run Windows Update in order to protect them from the vulnerability that made the virus possible? In both cases you're co-opting a computer without permission... the intended ends don't quite justify the means.
Slashdot Mirror
Maybe they meant "balk", meaning "hindrance".
Did anyone see anything from this JAXA webcast feed? All I saw was green, as if they forgot to patch in the signal.
Actually, the Range reports a precise liftoff time down to the millisecond, based on first motion of the vehicle. In this case, it was 7:43:44.074 p.m. EDT according to Spaceflight Now.
It might be nice if they had bothered with an official web site that contained any decent, up-to-date information about the mission. The "News" section is basically just the home page with nothing timely, and the latest entry on the "Press Releases" page is four days old.
You're right. Not only that, the border with Canada passes through the approximate middle of the rest of the Great Lakes (except around Isle Royale in Lake Superior, where it cuts much closer to the Canadian shore), so the "border zone" covers much less land there. Ironically, even though the map shows Michigan as being completely within the zone, TFA omits that state in its list.
I find humour in the fact that whenever a Wikipedia editor writes "Truth" in the edit summary, 9 times out of 10 the edit is not actual fact but rather POV, bullshit, or simple vandalism.
I know a couple who endowed a scholarship at their alma mater. They intended it to help promote women in computer science. But because of Title IX the scholarship can't have a gender-based requirement, so it's awarded to someone "whose presence promotes diversity".
The real problem is that test tubes come in racks of ten, and hot dog buns will still come in packs of eight.
Trouble is, it's still stuck using distilled water. I'm waiting for a hydrogen converter that can handle rainwater, or household greywater, or the aforementioned on-board pee tube.
I'm out of it... I was really hoping Google Android would be something that could walk around my house and help me find my keys.
The question you asked was, "Is it best to move on to another company or to stay where you are and try to get ahead there?", so let's ignore all the knee-jerk "all bosses are lobotomized PHBs" responses and assume that you truly want to leverage your experience and talents into a position with increased responsibility, authority, and (one hopes) salary.
The short and generalized answer is, moving on is better than staying put.
The IT worker always suffers under the role of the "man behind the curtain." As in, "Pay no attention to the..." If you're doing your job right, the major problems you're solving are never getting noticed by those who might have been affected by them. You can fight fires all day long every day and no one will know until that one time they smell a little smoke. Even those big projects where you shine and do a great job and bring it in ahead of time and under budget get forgotten the moment the first follow-on issue arises.
Because of this, tooting your own horn at your corrent job probably won't help much. You'll say, "look what I fixed" and hear "but this is broken." You'll say "look what I built" and hear "yes, but what about all this other stuff that needs doing?"
Add to that the inertia of those in positions above you. You didn't say whether they had already hired someone to fill that IT manager position above you. If they did, how long do you think it will be until they move on, or move up, and enable you to take that role?
The moment you're hired, you're pigeonholed into a specific role. Those who see you as just the "lowly IT person" won't be able to see you as a manager, no matter how well you demonstrate your leadership, logistical ability, and business savvy. At best, they might see you as "that awesome IT person" -- and will think of you as irreplaceable in the position you're already in.
Instead, if you move on to someplace else, you have the chance to put your knowledge and experience in the very best light, as you describe them in your résumé and in interviews. ("Spearheaded a project" sounds much better to a prospective hirer than "Sat through numerous interminable meetings before doing it all myself because no one could come to a decision" does to your current boss.) You also get to start with a blank slate with regard to what you might be capable of doing. Every time I've started a new job, I've been hired to do many things that I'd never actually done before.
At my first full-time job I was hired as a programmer and analyst at a university, with plenty of help desk work. Although my influence on decision-making grew somewhat during the time I was there, after several years it was clear that my boss had no inclination to move up or move on. There was nowhere for me to go, so I moved on.
Next, I was hired as a support specialist in a state agency, at a 10% salary boost. I was the team leader for many projects there, but when my boss quit and I had to shoulder most of his responsibilities, rather than promote me into his position they eliminated it. I wound up with all his work and none of his benefits.
I moved on to a privately-owned company and became their senior network admin with another rise in salary. I helped coordinate a major construction project of a new office (and no, I had no prior experience in this) that came in on time and under budget. After that I volunteered for several other big projects that effectively never left the wish-list phase, and wound up doing mostly day-to-day firefighting that never got noticed except in those rare failures. And my manager had been there for years and wasn't going anywhere. So I started looking around again...
One word of caution: when you start looking beyond the walls of your current job, be circumspect and anonymous. At this job, unbeknownst to me, the HR department had a policy of periodically checking the major job boards (Monster.com, etc.) for résumé postings from employees. Those they found were summaril
I think you mean "liable" not "libel".
Did they have to make it look like the floating torture droid from Star Wars?
Because the twelfth face of the dodecahedron is occupied by the mount.
That comment is ageist, sexist, and racist. Way to hit the trifecta.
If it were possible for a 15-year-old black male to have already had a long career with the Air Force as a registered nurse, and had a husband who has similarly served his country, he'd probably get the same slap on the wrist. Being a military veteran can get you a lot of slack from the cops, many of whom are vets too.
It might. Garmin also uses Navteq maps in its GPS devices -- in fact Navteq is Garmin's most important supplier -- and Garmin's stock price went into the dumper today on the NYSE because of fear that Garmin will have less influence, both in pricing and features, on Navteq when it's owned by Nokia.
IMO, NASA should mothball the Shuttle immediately and put all its effort into developing the Ares system. They would have to re-manifest some crews and hardware aboard Soyuz and Proton rockets for the next few years, but that would allow their current engineering talent to focus exclusively on the new system, avoid the brain drain that Administrator Griffin fears, and save a bunch of money in the process. I bet with focus they could have flight-worthy hardware by 2010.
Arthur C. Clarke said, "Trim this."
In 2000 I contributed a chapter to a book on U.S. launch vehicle history. Before I sent my final draft to the editors, I ran it through Turnitin. This I did as a form of self-preservation, because given that the vast portion of my chapter was heavily based on other sources, I wanted to be sure that I had done an adequate job of paraphrasing and attribution. (My scan, by the way, came up clean.)
Now, while I have some concern that a copy of my chapter resides on Turnitin's servers, I am fairly certain that no more than appropriately-sized excerpts will ever be reprinted there, and then only in cases of likely inappropriate borrowing. Moreover, I am happy that it's there, for this reason: it establishes a record of prior existence. No one subject to a Turnitin review will be able to crib from me without proper attribution.
None of this, of course, has prevented a substantial case of plagiarism of my chapter by a contributor to the Thor rocket page on Wikipedia.
Hilarious, his best work since his spoof of "Smells Like Teen Spirit." ...but call me an old fart with no awareness of current music, especially hip-hop -- I have no idea what song this is based on.
My desk neighbour has a U-505 submarine sitting on his monitor that he got last year at the Museum of Science and Industry. The mold for it is probably 50 years old and still going strong. (By the way, the new exhibition space for the U-505 is worth a trip to Chicago just to see that.)
If non-flight, space-related deaths are included, one would have to include Charlie Bassett, Elliott See, and C.C. Williams. All three astronauts died in T-38 crashes while in the line of duty for the American space program.
As others have said, most places in the U.S. this wouldn't work, since (1) corporate stores won't do discounts, and (2) only a jerk would negotiate a price at a mom-and-pop store that's already being undercut by the Wal-Mart and Costco down the street. (One exception: those cluttered electronics stores in New York City. Haggle to your heart's content there.) In China, except for higher-end shopping districts, negotiating the price is expected.
A problem with group-buy is this: when negotiating, one should always be prepared to walk away. My wife and I used this move in China several times, and it almost always resulted in an instant price cut. With 500 people, seems like it would be tough to get enough momentum to head for the door. That much mass takes that threat off the table.
Earlier this year, the Washington D.C. Metro held a competition to find a new voice for the subway's automatic announcements. Part of the reason for this was that riders had gotten too familiar with the old voice and had started to ignore the "doors closing" warning.
Seems to me that the coffee room eyes would have to be replaced periodically as well, because as people got used to them they'd start to ignore them.
I agree with the project's intent, but how does this differ from, say, writing a virus that forces remote computers to run Windows Update in order to protect them from the vulnerability that made the virus possible? In both cases you're co-opting a computer without permission... the intended ends don't quite justify the means.