kuzee

Elixir/Phoenix developers will get a lot of mileage out of the ability to quickly collect and inspect stats like this. This is really great and solves ~50% of the use cases for an outside error monitoring service while also making debugging specific instances easier.

This is truly fantastic, the use of an eink display so that it doesn't shout for attention but is always ready is such a good call and in my opinion worth the additional effort. Thanks for sharing and making the code available for others to read and learn from.

I'll pay you $5/mo if it includes an intelligent way to sync the images I take of my book pages to my Google Drive in an organized way, such as per book. Adding in text that was OCRd and therefore searchable would also be great. So far my manual process is moving photos in Google Photos (I'm on Android) which is so-so. I'm fine with ads if I'm not paying.

This is magic

Coming from Ruby and Python and a bit of node, Elixir encourages a really convenient mental model for thinking about small and large parts of your app in the same way. Net result is fewer bugs created, easier to write tests so you write more, and easy to debug when they do happen. And because of the fault tolerance, most production bugs are so transient they're not causing problems. I've run several small webapps with a few thousand users and the maintenance is minimal because of how solid the language is.