3) Competitiveness and ability to handle stress are not good reasons to promote one employee over another. Promoting the top performers at one level to a higher level is actually bad business practice. It ensures that everyone is promoted to their level of maximum incompetence. Studies where employees were promoted AT RANDOM showed better outcomes than when promotion was based on current employee performance.
The fact that it's not a good reason doesn't mean it doesn't happen. Business makes bad, short-sighted decisions all the time. Unfortunately, they're run by humans, who are also known for making bad, short-sighted decisions.
If your password policies fail to account for reality, then they're the problem. Thus, password policies are the problem, because clearly they don't account for reality.
Plus, how much market is there for shoebox-sized satellites? Universities and "satellite hobby clubs" would be interested, but there's a reason why SpaceX never built any more Falcon 1 rockets...
One nice thing about Apollo's method is that when you're coming back from the moon, you get to slow down for free (i.e. aerobraking). If most of your craft is going to be left in LEO during the return trip, you have to carry fuel to and back from the moon to use to slow down once you get back to LEO.
Ah, Slashdot, never change. I should be able to take apart my hardware and change it up in any way I see fit. I should be able to take apart my software and change it up in any way I see fit. I should be able to do whatever I want with my media, like time shift it, or format shift it, except skipping over the swear words. I shouldn't be able to do that.
Pedantic, maybe, but GC is not necessarily non-deterministic. The GC in some particular platform may be, but that's not a defining characteristic of GC.
Yes, multithread that file scan! That way, both your disk *and* your CPU can be pegged full-time, and any potential viruses won't have any CPU time or IO available to do anything nefarious!
Windows *does* do that; it asks permission for anything you don't have rights to do. I don't use MacOS a lot, but it seemed to be very similar to how OSX did/does it.
Now, if you meant "ask permission to execute any.exe not on the whitelist", then yeah, I don't know of any OS that does *that*.
Loss of a blade certainly means shutdown of the engine. This is normal, accepted, and accounted for. It has happened before on a Falcon 9 flight (shutdown of an engine, I mean, I don't know if a blade was thrown). It also happened during Apollo 13's second stage burn.
Even if the entire rocket was lost, it STILL doesn't mean loss of life. All manned rockets I'm aware of (and I'm not a rocket scientist or even a particularly devoted follower of rocketry) have launch escape systems, and they get tested; the one for Apollo was even tested semi-unintentionally; the Little Joe II booster that was carrying the capsule for the test blew up before the test was supposed to start, and the capsule separated and survived just like it was designed to.
Windows NT was written in C specifically so it could be portable. MS was so determined that NT be portable that it was originally developed on non-x86 hardware (i860) specifically so they wouldn't accidentally build in any x86-isms.
It should be illegal for me to carry a baseball bat (i.e. harmless) because you're mortally afraid of being attacked by a baseball bat (i.e. fear)? IMHO that's not how it should work.
So wait; the agile manifesto specifically says you should do "scrum-but", but if you do "scrum-but" you'll fail, and it's because you weren't doing pure scrum the way your expensive trainer taught you?
Agile is specifically designed to remove all choice and creativity from programmers. It is designed to give the power to the product and marketing department. When agile fails, it's because programmers don't like being held down, and product people don't concentrate on the important fundamentals, only the shiny surface.
Visual Studio for Mac is definitely Xamarin Studio with a different name. .NET Core is most certainly *not* Mono, it's an entirely different codebase.
3) Competitiveness and ability to handle stress are not good reasons to promote one employee over another. Promoting the top performers at one level to a higher level is actually bad business practice. It ensures that everyone is promoted to their level of maximum incompetence. Studies where employees were promoted AT RANDOM showed better outcomes than when promotion was based on current employee performance.
The fact that it's not a good reason doesn't mean it doesn't happen. Business makes bad, short-sighted decisions all the time. Unfortunately, they're run by humans, who are also known for making bad, short-sighted decisions.
If your password policies fail to account for reality, then they're the problem. Thus, password policies are the problem, because clearly they don't account for reality.
*woosh*
Plus, how much market is there for shoebox-sized satellites? Universities and "satellite hobby clubs" would be interested, but there's a reason why SpaceX never built any more Falcon 1 rockets...
One nice thing about Apollo's method is that when you're coming back from the moon, you get to slow down for free (i.e. aerobraking). If most of your craft is going to be left in LEO during the return trip, you have to carry fuel to and back from the moon to use to slow down once you get back to LEO.
Ah, Slashdot, never change. I should be able to take apart my hardware and change it up in any way I see fit. I should be able to take apart my software and change it up in any way I see fit. I should be able to do whatever I want with my media, like time shift it, or format shift it, except skipping over the swear words. I shouldn't be able to do that.
I know, right? Hammers are so hard to learn.
Pedantic, maybe, but GC is not necessarily non-deterministic. The GC in some particular platform may be, but that's not a defining characteristic of GC.
Yes, multithread that file scan! That way, both your disk *and* your CPU can be pegged full-time, and any potential viruses won't have any CPU time or IO available to do anything nefarious!
So, pretty much like any company ever, then?
Windows *does* do that; it asks permission for anything you don't have rights to do. I don't use MacOS a lot, but it seemed to be very similar to how OSX did/does it.
Now, if you meant "ask permission to execute any .exe not on the whitelist", then yeah, I don't know of any OS that does *that*.
I suspect that the companies receiving the USF funds don't see it as a failure. There's probably not enough "stick" to go with that "carrot" though...
Loss of a blade certainly means shutdown of the engine. This is normal, accepted, and accounted for. It has happened before on a Falcon 9 flight (shutdown of an engine, I mean, I don't know if a blade was thrown). It also happened during Apollo 13's second stage burn.
Even if the entire rocket was lost, it STILL doesn't mean loss of life. All manned rockets I'm aware of (and I'm not a rocket scientist or even a particularly devoted follower of rocketry) have launch escape systems, and they get tested; the one for Apollo was even tested semi-unintentionally; the Little Joe II booster that was carrying the capsule for the test blew up before the test was supposed to start, and the capsule separated and survived just like it was designed to.
Lacking what?
What about Windows' firewall makes it unreasonable? Honestly curious here.
They didn't even say that. All they said was that it was replacing CMD in the Win+X menu. How many people even use that menu?
Windows NT was written in C specifically so it could be portable. MS was so determined that NT be portable that it was originally developed on non-x86 hardware (i860) specifically so they wouldn't accidentally build in any x86-isms.
It should be illegal for me to carry a baseball bat (i.e. harmless) because you're mortally afraid of being attacked by a baseball bat (i.e. fear)? IMHO that's not how it should work.
Ah, but then that's not Scrum, then, is it?
Not sure if joking or just fails badly at statistics.
So wait; the agile manifesto specifically says you should do "scrum-but", but if you do "scrum-but" you'll fail, and it's because you weren't doing pure scrum the way your expensive trainer taught you?
Agile is specifically designed to remove all choice and creativity from programmers. It is designed to give the power to the product and marketing department. When agile fails, it's because programmers don't like being held down, and product people don't concentrate on the important fundamentals, only the shiny surface.
Python's open and standard too, that's why Python 2 is still the most common variant.
If you're financing your computers, maybe you should buy cheaper computers.