...which has reference #14 has Sen listed as the author of another article (can't find direct link), here's #14 though:
Sen, C. K. & Ghatak, S. miRNA control of tissue repair and regeneration. Am. J. Pathol. 185, 2629–2640 (2015).
I had played various Infocom games as a kid, simply amazing. Then recently "discovered" that there is this exciting corner of the Multiverse know as Interactive Fiction, which has been flourishing quite well for a long time. Just finished "Beautiful Dreamer" by Woodson, enjoyed that very much.
> It's offloading the cost of hiring on to prospective candidates.
Why is that a bad thing? The prospective candidates aren't entitled to anything, the burden should be on them to prove they have any capabilities for the job.
> What is the employer putting up? Generally nothing.
Totally incorrect, have you ever had to hire somebody? The initial phone screens alone to weed out the 99% of complete incompetents takes many hours/days. Even getting to the list of phone screens, involves many hours of sifting through resumes, where each resume is cleverly designed to hide the fact that the prospective candidate is incompetent.
I'm quite impressed with the Hololens, but keep in mind that it's a totally a first gen developer product, so was better than my expectations. Yes the field of view is a tad narrow, and yes, the gestures still don't pick up at much at they should. But the holograms look stellar, the position tracking is quite stellar, objects that are placed, stay placed very well while you move about, the effect works very well. The floating planets that my kids stuck on the living room ceiling, continue to stay floating there until somebody later comes by and moves or resizes them. I think this device will have a bright future.
71 device years, on an p2.16xlarge instance, I think the NSA could certainly come up with something way moar better in a shorter timeframe, assuming they haven't already done so.
I've been doing concurrent programming for 17 years, it's been pretty much the same game, at least with Java/C/C#/C++ which is my experience. The abstractions are helpful, but clearly no panacea. The most common problems I see today are with Tasks w/lambdas and Parallel.ForEach, where synchronization is either completely missing or misused, or unnecessary (i.e. a better design would have been to remove all shared state to begin with). The next main problem I run into, folks tend to sprinkle in concurrent code in an ad-hoc fashion, even using the understandable abstractions. That works fine, until it doesn't, with the "not working" state being rather difficult to detect.
My all time favorite is one of the original songs, but still a "style parody", Everything You Know is Wrong. But all songs, whether direct parodies or originals, are pure brilliance.
One can argue these topics until the cows come home, and possibly later. One can strongly argue for/against imperative programming, functional programming, OOP, design patterns, Design Patterns with Cool Names, Design Patterns as Implemented in Your Favorite Language, etc... At the end of the day, the only thing that matters is whether your team thinks your source code is structured or not. If you're on a team of one, well then you have your future self to contend with.
Despite the deluge of advice from the Innovation-thumpers of the many virtues of personal washing, I have yet to invent a flying car while standing in the shower thinking. (great song though).
Thanks for the mention of this, I'm quite interested, looking at their FAQ right now, curious to see how they handle latency. Do you notice any lag? Also, what FPS do you achieve?