We are—first and foremost—captains and pilots. But we must also be effective cockpit managers. On our automated flight decks, we must manage the various levels of automation available to us. Clearly, increasing levels of automation will reduce workload in most scenarios. However, we must change the culture that drives us to operate at the highest levels at all times. Automation lacks the ability to create flexible responses to unanticipated flight path requirements.
It was especially true decades ago, given the accident history of the 1990s, and remains poignant even with our better understanding of the limits of automation.
Thanks, I'll take the one that isn't engineered to impoverish all but the connected elite.
Those who've benefitted the most by holding bitcoins are a connected elite. They're the ones who had the education, technology, and resources to understand, use, and acquire units of the currency. As Bitcoin becomes increasingly popular in the mainstream (with people who've had less access to the aforementioned benefits), those in that small group closer to the beginning will enjoy a substantial rise in the value of their bitcoins. That's fair, of course, but don't pretend you're part of a populist movement.
Technical issues aside, there are people who want to see Windows become less popular. Operating systems are only interesting to people insofar as the software available to run on them. If developers stop supporting Windows, users will stop using it.
There is an upper limit on the number of bitcoins that can ever be created so the cost of generating new Bitcoins [sic] rises over time, and the value of Bitcoins [sic] rise relative to the available goods and services in the market.
If I understand correctly, his persuasion is fundamentally incorrect. As bitcoins are infinitely divisible, the market can decide the value of increasingly smaller units (which is impractical with physical commodities, like gold) in response to scarcity brought on by that upper bound, loss of coins, higher mining costs, hoarding, and so on.
An HIV or Hepatitis C test that delivered false negatives would be worse than useless, potentially giving positive patients a false sense of security. With that faulty sense, those holding incorrect results could leave their diseases untreated and risk exposing others. However, false negatives from 23andMe—provided a small advisory to its users—would leave them ignorant of conditions like Huntington's or BRCA the same as if they had never submitted a sample, whereas false and true positives would both prompt additional investigation on the part of the customer. In other words, if 23andMe gives a negative result, you still don't know what you didn't know before. If it gives a positive result, you'll be inclined to seek a medical opinion from a professional.
It's a pretty clear-cut case of regulation overreaching its boundaries and bearing on an innovative product that's helping to promote mainstream genetic testing.
Skilled engineers who wish to remain relevant and find greater success will educate themselves about new technologies and use whatever tool is best for the job. This isn't about "new hotness" as you put it, it's about willingness to move on from a given technology when superior alternatives exist. Done smartly, there is a great deal of value found in disrupting the status quo. That a project or team uses any given technology doesn't mean it should always be stuck there.
The Java language (not the platform, mind you) is antiquated and difficult to use compared to many new languages that have surfaced (I mentioned two). In its day, Java was among the best languages to get hard problems solved quickly. Today, demanding requirements for scalability and durability are the new normal. You can achieve these in Java, but doing so requires a lot more effort—in no small part to resistance to evolve the language on the part of its maintainers.
Can you explain what problems I wouldn't be able to solve with JavaScript that are solvable with Java? I've yet to encounter any. Maybe you can help me?
Average developers will continue using Java as forward-thinking engineers use Scala, JavaScript, and other progressive languages to solve real problems faster.
Slashdot Mirror
Drive your car to the edge, dude.
Captain Warren Van der Burgh gave a lecture at American Airlines in 1997 that addressed this topic. It was an engaging study of several scenarios where aircraft automation can defeat the intentions of and task-saturate flight crews.
From his conclusion:
It was especially true decades ago, given the accident history of the 1990s, and remains poignant even with our better understanding of the limits of automation.
How does this junk make it?
Thanks, I'll take the one that isn't engineered to impoverish all but the connected elite.
Those who've benefitted the most by holding bitcoins are a connected elite. They're the ones who had the education, technology, and resources to understand, use, and acquire units of the currency. As Bitcoin becomes increasingly popular in the mainstream (with people who've had less access to the aforementioned benefits), those in that small group closer to the beginning will enjoy a substantial rise in the value of their bitcoins. That's fair, of course, but don't pretend you're part of a populist movement.
Technical issues aside, there are people who want to see Windows become less popular. Operating systems are only interesting to people insofar as the software available to run on them. If developers stop supporting Windows, users will stop using it.
There is an upper limit on the number of bitcoins that can ever be created so the cost of generating new Bitcoins [sic] rises over time, and the value of Bitcoins [sic] rise relative to the available goods and services in the market.
If I understand correctly, his persuasion is fundamentally incorrect. As bitcoins are infinitely divisible, the market can decide the value of increasingly smaller units (which is impractical with physical commodities, like gold) in response to scarcity brought on by that upper bound, loss of coins, higher mining costs, hoarding, and so on.
That's faulty logic.
An HIV or Hepatitis C test that delivered false negatives would be worse than useless, potentially giving positive patients a false sense of security. With that faulty sense, those holding incorrect results could leave their diseases untreated and risk exposing others. However, false negatives from 23andMe—provided a small advisory to its users—would leave them ignorant of conditions like Huntington's or BRCA the same as if they had never submitted a sample, whereas false and true positives would both prompt additional investigation on the part of the customer. In other words, if 23andMe gives a negative result, you still don't know what you didn't know before. If it gives a positive result, you'll be inclined to seek a medical opinion from a professional.
It's a pretty clear-cut case of regulation overreaching its boundaries and bearing on an innovative product that's helping to promote mainstream genetic testing.
Are you able to understand the original source?
Skilled engineers who wish to remain relevant and find greater success will educate themselves about new technologies and use whatever tool is best for the job. This isn't about "new hotness" as you put it, it's about willingness to move on from a given technology when superior alternatives exist. Done smartly, there is a great deal of value found in disrupting the status quo. That a project or team uses any given technology doesn't mean it should always be stuck there.
The Java language (not the platform, mind you) is antiquated and difficult to use compared to many new languages that have surfaced (I mentioned two). In its day, Java was among the best languages to get hard problems solved quickly. Today, demanding requirements for scalability and durability are the new normal. You can achieve these in Java, but doing so requires a lot more effort—in no small part to resistance to evolve the language on the part of its maintainers.
Can you explain what problems I wouldn't be able to solve with JavaScript that are solvable with Java? I've yet to encounter any. Maybe you can help me?
Average developers will continue using Java as forward-thinking engineers use Scala, JavaScript, and other progressive languages to solve real problems faster.
I've little to add besides my agreement. Privacy cannot be assumed in public spaces. Nothing's more public than the Internet. Act accordingly.