376 karma · joined September 15, 2008
Floreo (http://floreotech.com) is an early-stage startup in Washington DC developing a first of its kind virtual reality platform to deliver children’s therapy. Our first product is focused on VR-based autism therapy. We are a multidisciplinary team of developers, doctors, designers, therapists, parents, and artists and we are working in the uncharted territory of VR for delivery of therapist mediated therapeutic experiences. This is a unique opportunity to build a highly challenging technically grounded product that has the potential of helping families in immeasurable ways. We are looking for a second developer to join our team with the following qualities: Game development experience using a commercial game engine such as Unity or Unreal is required Experience in all aspects of developing a game, from design to fine tuning multiplayer network latencies are highly desirable Experience specifically with VR is a plus Startup experience is highly desired as we are a small team used to wearing lots of hats Our stack currently includes, Unity (using CSharp), to implement the VR / in game experience. We are using “Google VR for Unity” AKA daydream/cardboard to build for iOS and Android. We are using in house developed 3D and audio assets. We run our own backend and API, written in Go on AWS.
Please send an email to jobs@floreotech.com and mention HN.
Also visit: http://floreotech.com/careers/
So ideally, in cases that you know before hand that you are going to need your willpower, like reading HN, you'd be better off arranging your life so that you don't have the option to spend as much time, and reserve your willpower for cases you cannot predict or control.
As far as I understand it, if you are big and have the resources, your best bet is still to develop separate native apps for each platform.
Right?
https://www.youtube.com/user/MatoJelic
I have no affiliation with him, but he is a brilliant trainer and he is a very lovely game narrator. I feel it is appropriate to talk about this channel, because I have not played serious chess in decades but just watching this guy go through these famous games, gave me such insight that reading this article (the on from OP) sounded rather naive.
I mean is it a new discovery that some frequencies create resonance and stop the convection and prevent oxygenation of the flame?
Or is it just using sheer power to "blow" the flame off? but instead of a blower, it just uses very high powered speaker in low frequency?
One saying "I've been here for long, I cannot remember of anybody" another one saying, "of course I know plenty of people who made a lot of money".
I think it means, as all other aspects of life, there are distinct clusters of people in this field, with little cross cluster exchange. Either you are in that group in which all of you make money or you are in the group that you and your friends none make much money.
One issue is when you want to hire people and you want to feel confident that you are offering them a "real chance" for financial success, even if it is a slim chance. I mean if you know that it is very likely that even when "you" have a win (whatever your goal is) and your investors have a win, still your employees don't benefit significantly, that will be a sad story.
In my limited experience, I've rarely faced any significant issues with EC2. I assume your threshold for issues must have been very lower than mine.
I read the copy, watched the video and until I scrolled down, I didn't get what it was all about, and why "must".
The reboot Podcast
StartUp Podcast
a16z
General:
Invisibilia
99 % invisible
planet money
EconTalk
But I definitely agree, OS X phones home (and other places) all the time. Everytime my phone rings my mac tries to connect to some apple server. ...
Although I don't know which character will be Paul Allen.
Definitely not Douglas Shafto.
a) only 10% of the fleet are running a version of the hypervisor that is affected by the bug
b) based on the turnover rate, they expect 10% to need rebooting under the customers by the date the bugs are being released.
c) 10% are running a combination of the affected hypervisor and vm's that are reasonably at risk of exploitation, other's may have the faulty hypervisor but either are being used as single tenant (there is no risk of someone breaking out and affecting someone else) or are running vm's that may not be able to break out depending on the nature of bugs.
Just speculating, any ideas?