ENadyr
Joined 10 years ago
Joined 10 years ago
One of my best hires ever was a VR dev we brought in as an intern. He became the backbone of our Unity/Unreal work, including some genuinely gnarly low-level haptics integration into the physics engine. On paper he didn’t look like the “obvious” pick: he’d majored in English Literature, largely because his (UK) school’s CS track was taught in a way that turned him off (they were still doing Fortran…). But he could build.
After our startup, Improbable scooped him up on the strength of that very real, shippable experience, and he’s now a senior SWE at Epic, doing exactly what he loves.
One practical thing that’s helped me find these kinds of people in startup interviews: optimize for calm + realism. My #1 goal is to get the candidate relaxed enough that I can see how they actually think and code. I often ask them to bring any public code they’ve written and we walk through it together. It’s a great way to surface judgment, taste, and real ownership that don’t show up on a resume.
While that ensured campmates could communicate, it unfortunately isolated us from the wider network—you had to choose one or the other. Also, regarding the UI: if you think Meshcore is bad, Meshtastic is worse. I spent most of my time teaching people how to navigate the clunky, overcomplicated, and inconsistent mobile apps. I’ll likely try building a custom app on top of Meshcore for this year.
For my future web stack the biggest chunk will probably be Daily https://docs.daily.co/reference/daily-js (by @kwindla) as the backbone of our teleoperation orchestration