Lead Software Engineer And Architect, Virtual World Research Group
Orlando, Fl, Us
As a research faculty in a contract-driven development lab working on collaborative ARMY research contracts, I typically did the following:Project Manager: Lead and manage efforts by disparate groups towards the desired deliverables. This included other UCF research labs, subcontracted businesses, paid employees within the same lab, as well as student interns and external community volunteers. I successfully lobbied the upstream ARMY research civilian to switch from the Opensimulator community codebase to the Halcyon fork of the same (Halcyon could not deploy on Linux, and other tradeoffs). Before leaving, I helmed the html5-based simulation client discovery / development effort.Principal Software Engineer: Architect system deployments, review and accept deliverables from other teams, mentor developers as needed. Discover platform deficiencies, evaluate available alternatives vs a custom solution, and drive the resolution of the dependency within budget and deployment constraints. Custom software included: MOSES Grid Management system, a collection of node and python services that allowed for simulator configuration and deployment onto hardware nodes completely through a web interface, including simulator state export/import, and console access. Many languages and platforms used, including: Windows, Centos Linux, Ubuntu Linux, C#, Node, Python, Javascript, Typescript, C++, QT/C++, Typescript, HTML and CSS.Research Associate: In addition to the software deliverables and technical achievements, the primary deliverable was data collected on this technology in human experiments ran by UCF and the lab I was attached to. I would participate in, and occasionally lead simulator-based training experiments on people, with the primary target being soldiers in leadership training exercises.