1,047 karma · joined November 21, 2014
http://kje.ca (email: ken@) http://linkedin.com/in/kennethjamesedwards
[ my public key: https://keybase.io/kejaed; my proof: https://keybase.io/kejaed/sigs/hitw0c0Sng-l_SdqQlTydZor7J1Ff1rQcRwZ3jtx3K0 ]
vdo.ninja and a couple of iPod Touch's (RIP) were really useful to give the trainers the ability to walk around the parachute loft to get up close and personal with a specific set of equipment. Combined with OBS, some powerpoint plug-ins, and vdo.ninja, we were able to bring something together that worked really well in no time at all.
For those looking to use something in between some of the horrible official camera apps and implementing something with this SDK, Cascable is really quite nice. I find it well worth the subscription.
Before the official SDK came out, I tried using this project that was working on reverse engineering the protocol for Fuji cameras:
https://github.com/hkr/fuji-cam-wifi-tool
Alas, I’m working with an X-T2 and it is not supported by the official SDK.
fp!
https://github.com/ocornut/imgui/wiki#about-the-imgui-paradi...
What pops into my head is to start reaching out to SpaceX. Their job posts indicate they will hire smart people and get them to work. The formal high design assurance type work from your medical experience will be a plus for sure. Step one just start reaching out.
Step two would be working on the background to explain why the medical SW experience is transferable. Know the DO-178C, DAL, ARP4754 buzzwords and flows, and I’d say even how the equivalent medical ones you are familiar with map over. This could even be a series of blog posts for you. It’ll show your communication abilities, your experience in the med side of things and then that you are working on the jump to aero.
It’ll form a good base for your knowledge, be a talking point when trying to make contacts and then in any interview. A banner at the top of the blog “I’m making the jump to aerospace, get in touch to hire me!”
But in the end at any established company, all the processes will be in place. If you join a 10 person startup then that would be tougher but that can come after a couple years at SpaceX. But I don’t have to tell you this part with your medical industry experience.
Good luck, feel free to reach out.
I've also worked with code bases with a formally defined state machine object/concept, with pre-defined states, events, and state transitions driven by events.
Question for the crowd: what would you call the non-state machine state machine in the first case?
The lineage ends up at a lot of the IEEE / ISO standards in use today for more formal systems and software development.