Posted by david927 11/9/2025
Ask HN: What Are You Working On? (Nov 2025)
I am building better dev tools for firmware and PCB developers.
For example, we have GitHub Action workflows that allow you to push builds to the connected EmbedHub project. Your EmbedHub project has fine grained release management - so for example only the git tagged releases will be shared with the customer, but the testing/QA team will get access to builds from regular commits on branches as well.
I am also building a physical device (called HAL) similar to the now discontinued EtcherPro[1] - which will connect to your EmbedHub account and have access to your releases. This will let you offload tasks like long term testing, mass flashing and provisioning of devices, and more.
My backhand is OK but my forehand sucks. Grip styles for standard handles usually end up favoring one side or the other. I'm making a handle shape that's easier to get the blade angle right on both sides. Hopefully a couple more iterations on the 3D printer and then I can have a functional prototype made.
Early use case is replacing API keys with identity tokens that expire, delegate, and prove possession and then can be used for easy step up to fine-grained authorization. There's some pretty interesting authorization stuff you can do, like having multiple parties sign off before a token is valid or requiring a series of micro-services sign a token for it to be valid.
And the repo is here:
https://github.com/igor47/csheet
If you play DnD, I would love feedback! Feel free to leave it as GitHub issues or discussion.
If you don't play DnD, you might still find the repo interesting. It's hono on bun, I render jsx server side and client side is all htmx. I use vercel's ai toolkit for the LLM interactions, which are super fun and work really well. I think this is a great use for AI actually. I've structured the code so the same services can be called either by the user via forms and routes, or via LLM tool use, so for every action in the code you can do it via either LLM or "manually".
I suggest adding an export function to make the characters more portable. Maybe export to PDF as well as JSON.
I think I got all of the important bits in place, now just working on improving the quality of life experience and bug hunting.
I have a lot of devlogs at https://www.slowrush.dev/news though at this point I am quite behind showing off the latest graphical improvements there.
Here is some more up-to-date gameplay footage: https://bsky.app/profile/slow-rush.bsky.social/post/3m523ft2...
It is a recipe app but better, and way more technically capable than anything out there. The goal is to make the best recipe app ever made. With bulletproof easy to follow recipes and smart features to make cooking simple. Everyone deserves good food at home, but good food is complicated and time consuming. An experienced cook can make good food quickly, cheaply and make it look easy. The idea is that Kastanj will have the knowledge you don’t so you can cook like a pro without having to spend years learning everything.
Backstory: I have a note where I write down practical problems I experience in life. I noticed over time that the amount of notes related to food and cooking was growing faster than anything else. I then began searching for a solution. I tried over 50 recipe apps, always the premium version if possible. There are some good apps out there but even the best ones only solved something like 50% of my issues. After enough frustration and search I just decided to start working on my own app. That was 4 years ago... It turns out that solving some of these problems where technically complicated to do, so now I understand why no other app could solve my problems. None the less, after 4 years of work, starting over from scratch 5 times, I have now landed on a solution that technically solves all my problems.
Going forward: Now I am working on filling the app with data and make it easy to use for normal humans. I am on purpose limiting myself to only perfecting the core functionality of what a recipe should be. I intend to launch sometime in 2026. The UI will be small and limited at first, but it is perfect for my needs. Therefore I hope it will also be perfect for someone else. Over time I will enable more advanced functionality and build it out based on user feedback. I know the backend can support 100% of my needs, but I don’t want to make it bloated. Therefore the UI is on purpose focused on only the most important things and then we will build it out with time, together with the recipe creators and end users.
https://play.google.com/store/apps/details?id=app.radarlove....
Just launched last month.
https://mail.gnu.org/archive/html/bug-gnu-emacs/2025-11/msg0...
This will add an iCalendar library to GNU Emacs, allowing packages in core and third-party packages to work with the format. More on the decisions I made and what I learned here:
Most shoppers spend hours to find the rights product. We’re fixing that with intent-based search that understands descriptions, images and personal preferences.
We’ve hit 25K+ searches in 4 months, growing 50% MoM, and built our own scraping system that makes product data collection 100× cheaper than existing tools.
Still early, but live. Would love feedback on search quality and result relevance.
PS! There are some products out of stock, this is expected, fixing it right now.
Skip any of these and even the fanciest ranking algorithms feel useless. Helping users bridge that gap is where relevance actually clicks.