coziestSoup
Joined 10 years ago
Joined 10 years ago
Osmo is a play system for tablets that brings together physical play and digital games to create magical educational experiences for kids.
After our acquisition by Byju's, we have been working on more awesome experiences at a larger scale than ever before, and we need more help.
You'll be part of a small engineering team working on the core vision algorithms that power Osmo. There's plenty of interesting challenges both on the research as well as engineering sides.
Email me at [email protected]
Granted, tentacrul seems like an established YouTuber, and this was probably the natural way for him to announce this, but I do hope more people/projects adopt this approach.
> Repl.it is my best friend as a developer. I use it every day. I didn’t realize I could work there!
This reminded me of when I first came to the US from India and started realizing that all the software I used (Windows, Gmail etc) and videogames I played were made by ordinary people like me.
And those who were already working remote. I do, and I've actually found it easier at meetings, where I'm not the only one on the screen anymore.
We are at the intersection of digital and physical play and learning. We make educational toys and games for kids. It's a little hard to explain, so I'll let our website do the explaining (www.playosmo.com).
This is a great opportunity for working in a small (5 right now), driven team and come up with creative solutions for CV tasks. We work closely with industrial designers and game developers to create a tightly integrated system that can detect toys placed in front of the tablet and make them come alive on the screen.
Osmo was acquired by indian edtech company Byju's last year, but we still operate as a scrappy, hyper-focused startup with our own product line.
Looks like the job post isn't up on our website yet, so feel free to email me with your resume (email in bio).
Sometimes its easy to predict how your code may need to be extended if you give it a bit of thought. In those cases, it might make sense to allow for easy extensibility. This is pretty rare though. Most times, you can't really predict what will be required of the code in the future. In those cases I prefer to bake as few assumptions into the code as possible, so when someone else is extending it in the future, they spend as little time understanding your code.