Why wouldn't you pretty much use this in every fighter plane we use. (I mean besides having to come up with upgraded electronics for the F-15, F-16, F-18, ETC) Why tie it to the F-35?

thing with you but I've seen similar stuff with self taught "experts". Let's see, I've seen experts that didn't know what the real difference between a list and array were, let alone knew what a map was. (CS 102 stuff.) Would always try to reinvent the wheel whether it was writing their own quick sort instead of using the built in one or building their own formatting routines that make the same strings as the ones already available in the class they're using. Then there's the whole issue of doing object oriented code because they're using C++ but having no concepts of some pretty basic OO ideas. (Like encapsulation or inheritance. Everything is public and everything is implemented multiple times it classes that really should be derived from one basic class.) Of course I'm guessing yours said the same stuff like "Oh my code is linear, if we need it to run faster get a faster computer." (It wasn't, it was order N^2)

I saw a report on I think 60 minutes probably 10 or 15 years ago where the black community was up in arms because they were losing out on scholarships. The complaint was they were losing them to the children of recent immigrants from Africa, a group that hadn't gone through the history of slavery because their ancestors didn't live in the US. (The whole point as far as they were concerned was this was to give a leg up to people that as a class had suffered through slavery and racism and recent African immigrants were not in this group but qualified for the scholarships and took them away from the people they were intended for.) To add insult to injury the recent African immigrants tended to be fairly successful and that lead to the complaint they didn't need the help anyway. But like you wrote, these immigrants were a self selecting group who went through all that hassle and they were more likely to be successful in the end.(It looks to me as though any group that intentional migrates will tend to do well because they're the driven to find success while people that are forced to migrate probably won't.)

It was one of a couple of TG-16 games they did on the Sega-CD. Funny thing was even though Lords of Thunder was basically the same game as the Duo-CD version the Sega-CD version of Dungeon Explorer was a totally new game.

from the Sega CD version of Dungeon Explorer .(There's an obscure reference.)

If everything I've read about it is true(and I mentioned this in another article here on /.) you literally can't get more than 40 hours of work out of people anyway. Oh sure, the first couple of weeks they do more work but then they get tired and slow and make mistakes. After a few weeks of that they're working more than 40 hours but aren't producing any more work. Go ahead, read stuff like Peopleware where they point this out. (That working overtime makes no sense, you don't get anything but pissed off employees.) Before anybody asks, no I don't work more than 40 hours a week. (And yes one of the big reasons is I'm old enough to recognize I don't get any more work done if I do. Plus the fact you do it and your manager quickly abuses it.)

Wait, you've seen them actually clean it up? I guess I have bad luck then because what happens in my experience is the company just keeps building up tech debt and think they'll never have to pay it down. (You know, like an idiot maxing out his credit card because he figures he only has to pay part of it off at the end of the month. It's practically forever before the whole bill is due:) ) Guess I'm gun shy since my experience is managers abuse it. (IE do the half ass version and then don't get time to clean it up until it collapses on a customer which is of course dev's fault.)

Just to be clear I've seen what you say work if it's along the lines of keep out features that aren't needed and we kept track that those features aren't there.(As you say tech debt or in this case reduced feature set.) What I haven't seen work is "We want all the features, we'll just do a half assed version of it and not keep track of the tech debt." turn out well. (I bring it up a lot but I always have this story of a communications protocol where my company tried to take the toy "proof of concept" version that made no attempt to implement large necessary portions of the protocol. Pretty much that was written under the directive of "Get a proof on concept in a day for a protocol that should have taken a week or 2 to implement." Basically the entire "handshake" portion was written with the idea that it would always work since there was no time to actually implement it. Not true in reality.) They spent weeks after that trying to get it to work and it still has serious issues. (It would have been quicker to just do it right in the first place. Of course now it gets dumped on me so I'm annoyed.)

Of course that was until they hired the manager that sucked at leadership/management but was awesome at company politics. End result was they laid the good manager off. (Since he thought it was stupid to use software engineers as tech support and actually tried to protect us from that shit, make sure our computers were up to date so we weren't frustrated, ETC. The rest of the company hated that since they absolutely love using us as their tech support. As best we could figure out the lousy manager considered the good one a threat so the crap one climbed the corporate ladder until they were above him and then used the layoff excuse to get rid of him.)

Modded me down for pointing out overtime has a long track record of not working or that managers make decisions so idiotic you wonder how they can't figure it out. (But us "older" workers know all about that.)

Amazing how many managers think you can save time by cutting quality isn't it? (Because what I see happen pretty much every time is it would have been quicker just to do it right the first time. You end up having to repeatedly fix the half-ass version until you get a working version.)

So this is made worse by the fact that any time anybody has actually checked they've found that long term overtime does not actually work. (IE you don't actually get any more work out of people by having them work more than 40 hours a week for long periods of time.) Us older workers (30+) already know this and don't play this game because it's pointless.(And apparently has been known for about a century so it's not a new concept.) However managers still want you to do that, mostly because far too many managers are completely stupid. (Something I feel justified in saying because I've seen way too many mind bogglingly stupid decisions from managers.)

You must be thinking of a different institute than I do. Professors don't teach, they're too busy doing their real job of research. The teaching is done by adjuncts and grad students.

Hell I'm one of the guys that harps on how quickly you can learn a language and even I agree with this. I mean I know I say that since I know C++ I was able to learn C# very quickly since the syntax is largely the same. But I'd still say it was at least a couple of weeks before I was pretty comfortable in C#. (No, I don't think it'd take any decent C++ guy months or years to get as good in C# but still it's not nothing either.) Mod the parent up. (I know I know, the mods can't because they're too busy modding down pointlessly, they have no points left.)

But since they're doing education with it, damn med students could use this to look at a virtual cadaver if they wanted to put in a little extra studying. (Since I bet seeing it in VR is a lot better than Grey's anatomy. Not as good as the real thing but they'll still be doing that.)