"If you want safe VTOL, just put a second engine on the Harrier."
Then you would have all the costs and issues of making the power transfer work, with an airframe that would have to be redesigned to accommodate the second engine, and no other benefits. It isnt as easy as you make it sound.
How can you tell? Just because the plaintiff says so? Some of those reviews look legit and yes a few look fake. I notice he doesn't complain about the obviously fake good reviews (how does a company in Cali get a positive review from a teen in New Jersey.)
If the images are anything to go by, then one of them is a Hasidic Jew from Israel, another is an actress in Chicago, and another is some guy in New York.
Unless they aren't, in which case their picture icons are being used in violation of Copyright, unless they have written permission from the image owners...
The stories about jobs and careers are getting so tiresome. I realize Dice bought Slashdot to datamine the comments (free focus group!), but it seems like half the stories are a variation on the same these days.
It's the non-engineers.
They have this misconception that people used to dealing with the intricate semantics of programming languages are going to be unaware of the intricate semantics of English. Therefore, if they ask a question once, and do not get an answer they like, they will repeatedly ask the same question in different guises, hoping to obtain the answer they wanted to hear.
This really comes down to who is more patient than whom.
I usually attempt to buffer my answers in order to soften the blow, but you can ask the same question as many ways as you want, and the answer will likely not change, so long as it is fundamentally the same question. And I usually have the patience of Job. However, there was one incident where I was up against a deadline, and was being asked to "just cobble together something that works, and we'll (read: you'll) fix it (read: in a binary compatible way) later. Which was an impossibility (I was working on some very complex database code written in C++ which did subschema definitional enforcement on an upper level database schema, and the semantics had to be correct for the data stored in the binary backing store to be usable going forward, when we did the next update). The code had to be *right*, as opposed to *right now*, and the time difference was important.
We had a UI person who was in a management position, and they brought her over to argue their case that immediate was better than correct (correct would fit under the deadline, but only if everyone left me alone to finish the code). The UI person was constantly revising the UI in each release, and each release was practically a full rewrite. And she did not understand why I could not write my code the same way she wrote hers. Finally having had enough, I explained "It's OK if your code is crap; you are going to rewrite it in the next release anyway. My code has to work now, and it has to continue to work going forward, and therefore it needs to be correct. I understand that you are feeling the approaching deadline. So am I. However, while your code can be crap, mine can't be because I have to maintain it going forward. Now if you will get the hell out of my office, I will be able to finish the code by the deadline."
Needless to say, there were some ruffled feathers. The director of engineering sided with me. I completed the (correct, rather than expedient) code by the deadline, and the product didn't turn into unmaintainable crap vis-a-vis the update process going forward.
What's the moral to this story?
Well, with specific regard to DICE:
(1) Repeatedly asking the same question in different ways is not going to get them a different answer, if the first answer was correct. Any other answer than that answer would be incorrect, for the question asked.
With specific regard to the current topic:
(2) Engineers who actually reliably, repeatedly, and consistently deliver what they are asked to deliver, within the timeframe that was agreed upon, can, and often do, wield more authority than the managers nominally set above them in the food chain, so it's not like going into management is going to give you any more real authority than you already have by way of your relationship with the team, and their trust of your judgement.
A management path can be a good idea if:
(A) You want more perks (stock options, etc.), although in a good company, if you are a great engineer, you will get those anyway
(B) You are tired of doing engineering for a living (which probably means you didn't qualify as "great engineer" under option 'A' anyway)
(C) You feel you would be more useful and/or happier in such a position (but if your happiness is based on power, don't expect it will necessarily follow)
(D) You are an OK (but not great) engineer at a company which engages in age discrimination, and you are happy to continue working for such a company going forward, and it's your only way to do so (at which point, I pretty much need to question your personal ethics)
Other than that... DICE: Asked and Answered. Please go on to the next survey question.
Show me a pilot that has to rely on their instruments and I'll show a pilot who can't fly.
Contrarywise, show me a pilot who *can* rely on their instruments, and I'll show you one who can land at SFO in the fog.
While there are wealthy pilots, most of us are of modest means. My (small) car is paid off so I spend the equivalent of its payment on my hobby during the on season, and that amount will go down once I finish my license. I won't need to buy my own glider outright, but if I do decide to do so, there are perfectly adequate specimens for sale in the $10k-$20k range.
Sure, and how much does it cost to store the thing, to have it launched, and do whatever else has to be done with a glider? I know powered aircraft are often white elephants in that respect.
As for time, I fly one day per week - sometimes two, sometimes zero. On the days I do fly, I still have time to mow the lawn, cook dinner, work on household projects, and even watch a movie with family.
I don't have a day a week to train so I could legally (under the sort of regime being proposed) fly my model aircraft. And they'd cost that same $10k-$20k once all the proposed equipment to do things like respect NOTAMs and restricted areas is put in. Because no one would make such equipment for hobbyists, they'd make it for the commercial market.
That's last year. It's been replaced by systemd.
Is systemd written in JQuery?
The obvious solution is to just make sure they never go out of business. Too big to fail.
I think you maybe mean "Too much personal data to fail"... which is an incredibly disturbing thought.
Do you defend every company which charges premium prices for a product where they limit your ability to do something every computer has been able to do for the last 50 years
Of course.
I will happily defend IKEA for selling me a chair that is limited from being able to do *anything* "every computer has been able to do for the last 50 years".
Except, you know, being sat on. If I can't sit on the chair, I'd be pretty unhappy. On the other hand, not every computer in the last 50 years has been large enough or flat enough to sit on. You gotta draw that line somewhere!
A near miss is defined as 500 feet:
http://flighttraining.aopa.org...
According to the American Helicopter Services & Aerial Firefighting Association, airtankers fly between 150 and 200 feet:
http://www.ahsafa.org/?page_id...
The article reports a drone altitude of 800-900 feet. Let's take the most pessimal separation from these numbers: 800 - 200 = 600. That gives them a buffer of 100 feet in which this was *NOT* even classifiable as a near miss; there was no danger of a drone to aircraft collision, unless you are claiming that the drone pilot intended to fly the drone into the DC-10 airtanker.
You will find elsewhere on the AHSAFA site that the aircraft do not "dive-bomb" the fires; a fully loaded airtanker had a heck of a lot of inertia, and it's not really an option; they are long, low runs. I refer you to the site however, because I doubt you'd trust my (anecdotal) personal experience with U.S. Forest Service airtankers.
Student pilot here, you're wrong. I fly for a hobby and will never earn a living doing it so I have no fear of lost income, but drones are scary because they could kill me.
A lot of things could kill you. Most likely your own piloting, statistically.
Nobody wants draconian restrictions like mandatory licensing
On the contrary, a lot of people want draconian restrictions like mandatory licensing and restrictions on sale of such vehicles. Which will basically kill their use by hobbyists (except relatively wealthy ones with a ton of time, like yourself). Spend a shitload of time getting a license, then pay the ridiculously inflated prices for a US-legal version of the equipment... ain't nobody going to do that.
Nearly homogeneous workforce? You haven't seen tech workplaces. There's Americans, Indians, Chinese, Koreans, and Europeans (both eastern and western) all well represented. Plenty of diversity.
Mystics always hope that science will some day overtake them. -- Booth Tarkington
