Not surprised, he’s a friend whom I watched build the game over a few years in the 2010s. He was EXTREMELY thorough in the playtesting, it set such an unrealistic expectations for me with games I play now
I really wish that there was a product that tags the LLM's thinking steps to the code that it's generating or modifying. Comments aren't sufficient as it's hard to track them across edits. Think something along comments in Google Docs: "I modified this block to prevent a race condition."
That would help me understand what the model is doing way better.
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.
Meshcore seems like a much better choice for messaging in dense-node environments. I tried to set up a Meshtastic network for my Burning Man camp this year, and since default builds have historically been crippled by retransmits, we made a concerted effort to give camps their own frequency slots.
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.
Agreed. Ran the comms for my burning man camp and everyone kept getting confused with the channels mess among other usability issues. I like where Mesh core is going, just wish the repeater nodes could run on gateway hardware so they don’t become the choke point with a half-duplex radio (bs like 8 full duplex channels on the RAK wireless gateway)
For the Camera? You don't want to know, it's a PDF that's in Chinese that for a C++ SDK in Linux!
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
I got excited reading this thinking this can help me with the SDK for a stereodepth camera I'm working with only but read then reading it's for the Next.js stack :sob:
On a separate note I like the retro DOS feel. Will probably look at this again properly when I build out the web side of my RaaS offering.
Please have an option for local processing. I would love to be able to use my locally running Gemma 3n model on my phone for low latency and for them to work without internet connectivity.