Building `nuqs`, a type-safe search params state manager for React frameworks:
🔗 https://nuqs.dev
🦋 @nuqs.dev
🎥 youtube.com/@47ng-dev
🟣 twitch.tv/francoisbest
🏠 francoisbest.com
I'm coding because it's fun, and prompting makes it not fun for me. Tab-completion is useful to go faster, because you remain in control.
I'm coding because it's fun, and prompting makes it not fun for me. Tab-completion is useful to go faster, because you remain in control.
Going from a high distrust of AI agents, to planning how to build my entire software production around one tool, to ditching it completely after realising how much control I'd be waiving.
OSS 4 ever.
Going from a high distrust of AI agents, to planning how to build my entire software production around one tool, to ditching it completely after realising how much control I'd be waiving.
OSS 4 ever.
I'm going to go back to coding by hand for a bit, see if I can still find that joy of thinking about a problem, devising a solution, implementing it and iterating on making it good, tested and looking nice without getting distracted. A sort of brain workout 🧠
I'm going to go back to coding by hand for a bit, see if I can still find that joy of thinking about a problem, devising a solution, implementing it and iterating on making it good, tested and looking nice without getting distracted. A sort of brain workout 🧠
It's a good tool overall. The extensibility with skills, hooks, commands, agents, plugins could even become a standard for malleable software.
But the fact it's closed source, and Anthropic's aggressive move against OSS integrations is 😬
It's a good tool overall. The extensibility with skills, hooks, commands, agents, plugins could even become a standard for malleable software.
But the fact it's closed source, and Anthropic's aggressive move against OSS integrations is 😬
"We can fix it later in post"
"It's a temporary fix"
Famous last words.
"We can fix it later in post"
"It's a temporary fix"
Famous last words.
When I finally caved in and checked the code (can't help it), it was a jumbled mess. useEffect everywhere, memory leaks, crashed the browser in the process.
When I finally caved in and checked the code (can't help it), it was a jumbled mess. useEffect everywhere, memory leaks, crashed the browser in the process.
That thing would have taken me weeks if not months to build in C++ 10 years ago (the Web{Audio} API takes the credit here).
But something changed.
That thing would have taken me weeks if not months to build in C++ 10 years ago (the Web{Audio} API takes the credit here).
But something changed.
I did some of the initial work myself, and let it grind for the rest. It did a good job.
But the real 🤯😱 moment was building the EQ & Compressor audio playground.
I did some of the initial work myself, and let it grind for the rest. It did a good job.
But the real 🤯😱 moment was building the EQ & Compressor audio playground.
Processing is the WebAudio API. Crazy what we can do with off-the-shelf nodes. Next step is to implement a custom algorithm (gate and de-essser).
Processing is the WebAudio API. Crazy what we can do with off-the-shelf nodes. Next step is to implement a custom algorithm (gate and de-essser).
cc @jherr.dev @rwieruch.bsky.social
cc @jherr.dev @rwieruch.bsky.social