ikornaselur
Joined 11 years ago
Joined 11 years ago
Tips weren't a part of my friends income. The restaurant/bar paid them a salary.
I was having Opus investigate it and I kept building and deploying the firmware for testing.. then I just figured I'd explain how it could do the same and pull the logs.
Off it went, for the next ~15 minutes it would flash the firmware multiple times until it figured out the issue and fixed it.
There was something so interesting about seeing a microcontroller on the desk being flashed by Claude Code, with LEDs blinking indicating failure states. There's something about it not being just code on your laptop that felt so interesting to me.
But I agree, absolutely, red/green test or have a way of validating (linting, testing, whatever it is) and explain the end-to-end loop, then the agent is able to work much faster without being blocked by you multiple times along the way.
I had a blog post somewhere to show the testing and results, but can't seem to find it at the moment though.
There were two reasons for my change, the Alacritty devs are really obsessed with speed, which is good, but.. means less features, even _optional_ features like ligatures. I like ligatures, and because they slow down the rendering slightly the alacritty devs do not want to include it[0]
The other reason is that I wanted a way to have my terminal have two different colorschemes, light for the day and dark for the night. It seems that it might be supported now with alacritty[1]? But it does also seem like you need an external script still to do it..
I went with WezTerm because it supports both natively, everything else feels the same TBH, but the fact that WezTerm has more features that are optional, is what I liked.
Notiflux (https://github.com/ikornaselur/notiflux): a small WebSocket broadcast server, the idea being that clients connect with WebSocket (such as a website) and then any source can send a POST request to the API to broadcast messages, allowing for real-time functionality from servers that don't support WebSockets, or you might have multiple sources that each might broadcast messages.
Auth is done by Notiflux having a public key and the sources have the corresponding private key, JWT tokens signed with the private key include topics and scope (subscribe or broadcast to the topics). Clients would auth with an API for example, get a JWT with maybe a 10 second expiry, use it to subscribe to the topics that the API would then broadcast to through Notiflux.
It was an excuse as well to play with WebSocket in Rust and learn a little bit about the Actor Pattern.
If I would continue I'd want to explore how well it scales, how much traffic it could handle and look into horizontal scaling, but I feel like it's complete enough as a toy project.
I've used zenpen.io for years, it persist just to local storage in your browser so the content is there when you open the page back up. Wouldn't count on it for persistence, but it's my absolute go to for quick ephemeral note taking
It's probably my favourite way of learning a new language, as it's simple enough to understand and implement
We he done this since our first year dating and now have multiple "Year X" albums that we sometimes pick up and go through.
We do also have a Google Home Max that is connected to a shared album we add photos to, which we keep in the kitchen and see latest photos pop up there, which we love seeing. But the physical albums are great because we hand picked those photos while going through the events of the year.
So in my opinion, there's no reason not to also have physical albums
What benefit does Graphite provide further?
Main pain point I imagine is dealing with rebases? What else?
Like if Github had the source for github public on github? Sounds a bit weird though, as its not "open sourcing itself", what ever that would really be
Edit: actually, I'm more confused now. Zed is just an editor? Not a platform?
Never finished it because I kept having to tweak and remeasure, but now I can definitely go back and finish it!