343 karma · joined April 30, 2010
This is the alternative right now: https://www.nytimes.com/wirecutter/blog/best-kindle-accessor...
[ONSITE in SF] Mechanical Engineer with >= 2 years of experience.
[ONSITE in SF or REMOTE] Electrical Engineer with >= 3 years of experience.
Both roles are to support development of our glasses product as well as future products. This involves prototyping and executing on feature additions, building testers for use on production lines, root-causing problems.
Email me john@solreader.com to chat more.
Any Android exports out there have a sense for how hard it'd be to get root access to something like this?
My wife, toddler and I were liveaboards on a 34' Hunter sailboat for 2.5 years in the Berkeley Marina. It was a blast for that season. I would recommend it if you like sailing, boats, minimalist living, and maintenance/tinkering. I would not recommend it if your main goal is to save money. In retrospect we probably did save money, but not that much, and definitely not an amount that would justify the amount of time I put into the boat (though I found boat work very satisfying).
So I built some hardware to interface with the SeaTalk network, the AIS radio (and a modern GPS) https://github.com/johnboiles/Helm-hardware https://github.com/johnboiles/Helm-firmware
And a Python proxy running on a Pi to pass messages back and forth across the network. https://github.com/johnboiles/NMEAProxy
And an iOS app that could drive my autopilot https://github.com/johnboiles/helm-ios
Since my proxy spoke the NMEA standard, you could also hook up with other apps like iSailor and get all the sensor data + gps + AIS data. https://apps.apple.com/us/app/wärtsilä-isailor/id398456162
To my knowledge, 0 other people have ever used any of this but I've always been proud of it :)
I wonder if it could be doing multiple small writes on every operation -- I could definitely imagine small writes getting very costly, especially with wear-leveled file systems that might be moving around pages on even small writes.
sqlite3_initialize();
sqlite3 *db;
sqlite3_open("/data/sqlite.db", &db);
char *err = 0;
sqlite3_exec(&db, "DROP TABLE table_name;", NULL, NULL, & err); // This takes ~5ms even when table_name does not existAnyone had experience running SQLite on low-power embedded platforms? Is this expected performance?
I'm using ESP32-S3 chips in a project. Rust support is really nascent and I can't afford to burn too much time on fixing tooling & recreating libraries. Though it does sound kinda fun.
But I imagine there's a chicken/egg challenge where it's hard to see Rust on embedded platforms get more mature unless it gets more adoption and it's hard to imagine a significant uptick in adoption unless it gets more mature.
Modern C++ is getting a little better all the time. And perhaps someday Carbon could be a smoother path to modernity because of its focus on migrating existing c++ codebases.
The main diff though is that Twitter for a moment in time started taking some shots. Not that they were all the best shots. But for my first two years there it felt like the company took nearly 0 shots. That shift happened with Kayvon.
Kayvon was a huge driving force behind all the interesting product efforts of the last few years: Spaces, Fleets, topics, etc. Twitter went from not iterating on product (remember when Twitter's only change in several years was to change the star to a heart?) to starting to take some shots. Behind the scenes he was often pushing against significant headwinds that resisted product change (not the least of which was the internal 'sacred cow' that all things must be built with Scala and only run inside Twitter's on-prem datacenters).