What matters here is that mistakes were obviously made. It matters not one bit whether they were made by stupid people. Stupid people have as much right to vote as smart people.
Not in the US. In the US, RA's get about the same money - about $15k depending on the field they're in. But that's as a student, its only supposed to be enough to live on while you get through school. The value you get out of being an RA is not a paycheck, its earning potential (supposedly).
Embarrasingly parallel implies NO communication is required. A typical application that runs on one of these machines, and yes, not only have I seen them, but I have written them, and am developing one right now, is an explicit PDE integration scheme that requires the communication of pseudo boundary conditions across the decomposed sections of the solution domain. Communication costs are very nontrivial in such a "best case" scenario.
As algorithms grow in complexity, for example to add adaptive capability, communication costs rise correspondingly. The scalability of a REAL state-of-the-art application that runs on these machines is not at all linear. Rest assured that you should be impressed with what has been done with the ASCI program, because its damn impressive.
If you know the temperature of the air she's falling through at that height, you can figure out the temperature on her suit by figuring out the temperature jump across the shock that will form in front of her, and then the temperature increase of the air as it exchanges kinetic energy for internal energy (as it slows down, coming to rest against her suit, it gets compressed and gets hotter).
Both of these things only depend on the Mach number and the properties of air, so you can calculate them very easily. The temperature on her suit will be about 21 degrees F. Not exactly "burning" temperature.
There are additional mechanisms for heat generation due to friction, but they won't make her suit get much hotter than 21 degrees F.
T2/T1 = 1.32 for a normal shock at M=1.5.
After, that, adiabatic compression would give
T0/T2 = 1 +(g-1)/2*M^2, where M=.7 is the post shock Mach number.
So that gives T0/T1 about 1.45. At 165,000 ft. you're in the isothermal layer that averages about -70 deg. F., or 203K. So the stagnation temperature on her suit would be about 21 deg. F.
So, nope, she wouldn't burn up. Even if you consider viscous heating, the turbulent recovery factor would be O(1), so she's not going to feel anything much hotter than that.
My point is not that there aren't bad managers, but that managers don't need to have the technical skills of their underlings to effectively manage. The things you mention are
grievous managment errors, but the way to avoid that is not to have a manager who knows the differences between private inheritance in smalltalk and C++. That is the point I'm making.
I hear all the time people bitching and moaning that "their boss doesn't even know Perl" or whatever. I think that shows a real tunnel vision on the part of the technical worker.
A manager's skill set definitely does include being able to effectively place talent, how to estimate the scope of projects, etc. But that's a different ballgame than what the guy who is writing the actual code needs to know. The "He can't even declare a variable!" argument is totally unconvincing. "He can't estimate the scope of a project" is a real complaint. I've suffered plent of mismanagement as a tech guy myself, I know all about it. But I also get sick of the hollow complaints about the boss who doesn't spend time coding.
Depending on the security level employed at your workplace, remember that a simple keystroke monitor doesn't care WHAT you're running. You type, it captures, end of story.
What damn good is the barcode? I don't get it. As far as I can tell it "accelerates" the typing in of a URL. That's not exactly the biggest barrier to accessing the web, now is it? If the CueCat software, on the other hand, is sending info on people about what they're scanning, not only will it be useless, but people will avoid it like the fascist plague that it is. Either way this company is screwed.
RedHat is a consumer product. The vast majority of RedHat installs have no "sysadmin." They have a person who clicks a few buttons to install the damn thing and that's that.
When a Win98 box is exploited, is it the syadmin's fault? That question doesn't even make sense. And neither does it make sense to say that poor sysadmins are at fault for RedHat exploits.
Come on - internet access is cool, its even occasionally useful. But rural communities have been around forever and they will be around forever, internet be damned. To say that they "will not survive" without high speed access is just silly.
ASCI White is the only machine doing 12 TeraOps. The next fastest is a trio of 3 TeraOp machines at each of the 3 ASCI centers (LLNL,LANL,Sandia).
As fast as 12 TeraOps is, its still far, far too slow to do real 3d, first principles physics simulations that involve a wide range of scales (which most real problems do). When they get to 1000 TeraOps, we'll be getting somewhere.
If they are an MS outfit, forget it. It's a huge mistake. System administrators? Fire them all and hire a new crew. Secretaries? Expect nothing to get done in the next 6 months (if ever again).
There is a tremendous amount of inertia involved in this type of thing. If you're creating your own shop, great - load it up with Linux boxes (I hope your shop is mostly engineers and not secretaries though). But don't try an en masse shift of a workable shop. That would more likely than not be a disaster.
When will people understand that it doesn't matter if Napster users are all angels (and they're not, btw). It doesn't matter if they go out and buy 20 albums for every song they download. It doesn't matter if Napster generates more revenue. It doesn't matter if Napster is their biggest break since the microphone.
What matters is that Napster has removed the artist's say in what happens to their music. If artists want to be stubborn and miss this "great opportunity," that's their right, and it ought to be respected. Pretty simple.
Slashdot Mirror
So the ballot was flawed in 1996, too. The only difference being it didn't matter in that election. Now it does, and deserves due attention.
What matters here is that mistakes were obviously made. It matters not one bit whether they were made by stupid people. Stupid people have as much right to vote as smart people.
74% reporting in FL. Bush is ahead by 4 percentage points. That's it...
51% Bush
47% Gore
Done deal. Bush is prez.
Not in the US. In the US, RA's get about the same money - about $15k depending on the field they're in. But that's as a student, its only supposed to be enough to live on while you get through school. The value you get out of being an RA is not a paycheck, its earning potential (supposedly).
Embarrasingly parallel implies NO communication is required. A typical application that runs on one of these machines, and yes, not only have I seen them, but I have written them, and am developing one right now, is an explicit PDE integration scheme that requires the communication of pseudo boundary conditions across the decomposed sections of the solution domain. Communication costs are very nontrivial in such a "best case" scenario.
As algorithms grow in complexity, for example to add adaptive capability, communication costs rise correspondingly. The scalability of a REAL state-of-the-art application that runs on these machines is not at all linear. Rest assured that you should be impressed with what has been done with the ASCI program, because its damn impressive.
If you know the temperature of the air she's falling through at that height, you can figure out the temperature on her suit by figuring out the temperature jump across the shock that will form in front of her, and then the temperature increase of the air as it exchanges kinetic energy for internal energy (as it slows down, coming to rest against her suit, it gets compressed and gets hotter).
Both of these things only depend on the Mach number and the properties of air, so you can calculate them very easily. The temperature on her suit will be about 21 degrees F. Not exactly "burning" temperature.
There are additional mechanisms for heat generation due to friction, but they won't make her suit get much hotter than 21 degrees F.
Does that make more sense?
T2/T1 = 1.32 for a normal shock at M=1.5.
After, that, adiabatic compression would give
T0/T2 = 1 +(g-1)/2*M^2, where M=.7 is the post shock Mach number.
So that gives T0/T1 about 1.45. At 165,000 ft. you're in the isothermal layer that averages about -70 deg. F., or 203K. So the stagnation temperature on her suit would be about 21 deg. F.
So, nope, she wouldn't burn up. Even if you consider viscous heating, the turbulent recovery factor would be O(1), so she's not going to feel anything much hotter than that.
My point is not that there aren't bad managers, but that managers don't need to have the technical skills of their underlings to effectively manage. The things you mention are
grievous managment errors, but the way to avoid that is not to have a manager who knows the differences between private inheritance in smalltalk and C++. That is the point I'm making.
I hear all the time people bitching and moaning that "their boss doesn't even know Perl" or whatever. I think that shows a real tunnel vision on the part of the technical worker.
A manager's skill set definitely does include being able to effectively place talent, how to estimate the scope of projects, etc. But that's a different ballgame than what the guy who is writing the actual code needs to know. The "He can't even declare a variable!" argument is totally unconvincing. "He can't estimate the scope of a project" is a real complaint. I've suffered plent of mismanagement as a tech guy myself, I know all about it. But I also get sick of the hollow complaints about the boss who doesn't spend time coding.
Depending on the security level employed at your workplace, remember that a simple keystroke monitor doesn't care WHAT you're running. You type, it captures, end of story.
What damn good is the barcode? I don't get it. As far as I can tell it "accelerates" the typing in of a URL. That's not exactly the biggest barrier to accessing the web, now is it? If the CueCat software, on the other hand, is sending info on people about what they're scanning, not only will it be useless, but people will avoid it like the fascist plague that it is. Either way this company is screwed.
RedHat is a consumer product. The vast majority of RedHat installs have no "sysadmin." They have a person who clicks a few buttons to install the damn thing and that's that.
When a Win98 box is exploited, is it the syadmin's fault? That question doesn't even make sense. And neither does it make sense to say that poor sysadmins are at fault for RedHat exploits.
It would be a matter of "intent."
Come on - internet access is cool, its even occasionally useful. But rural communities have been around forever and they will be around forever, internet be damned. To say that they "will not survive" without high speed access is just silly.
ASCI White is the only machine doing 12 TeraOps. The next fastest is a trio of 3 TeraOp machines at each of the 3 ASCI centers (LLNL,LANL,Sandia).
As fast as 12 TeraOps is, its still far, far too slow to do real 3d, first principles physics simulations that involve a wide range of scales (which most real problems do). When they get to 1000 TeraOps, we'll be getting somewhere.
Besides, this breaks the usefulness of the net in a major way. No diagrams, no figures, no pictures? Relatively useless.
If they are an MS outfit, forget it. It's a huge mistake. System administrators? Fire them all and hire a new crew. Secretaries? Expect nothing to get done in the next 6 months (if ever again). There is a tremendous amount of inertia involved in this type of thing. If you're creating your own shop, great - load it up with Linux boxes (I hope your shop is mostly engineers and not secretaries though). But don't try an en masse shift of a workable shop. That would more likely than not be a disaster.
When will people understand that it doesn't matter if Napster users are all angels (and they're not, btw). It doesn't matter if they go out and buy 20 albums for every song they download. It doesn't matter if Napster generates more revenue. It doesn't matter if Napster is their biggest break since the microphone.
What matters is that Napster has removed the artist's say in what happens to their music. If artists want to be stubborn and miss this "great opportunity," that's their right, and it ought to be respected. Pretty simple.
Flat