Daniel Cadenas

This was more useful than I thought it was going to be: "From all the text you know about me from our conversation history, can you analyze from my typing errors which are the keys or key combinations that I find most difficult and where I make the most errors?" #AI

I made a tool to fuzzy find nostr relays from command line:

GitHub

GitHub - dcadenas/nostr-relay-select

Contribute to dcadenas/nostr-relay-select development by creating an account on GitHub.

Gave

Undocumented Nostr Event Kinds Tracker

a visual upgrade ❤️ and made kind detection smarter, accepted kinds are now properly filtered out.

Nice tool to find the best coding font: https://www.codingfont.com/

An experiment on geohash-scoped relays: g-tagged events must go to the matching relay, but non-tagged events are accepted too

Geohashed Nostr Relay

There’s something special about Norwegians and sculptures

Something I’ve been noticing when vibe-coding a topic I don’t fully get yet: I make a ton of mistakes. Then I end up reading a bunch of code, adding logs everywhere, and writing even more. It feels chaotic, but weirdly effective. Some people say this newer way of programming is making us worse developers… but is it? Are we worse off now that we don’t write in assembly anymore? Or maybe we’re just learning at a different layer of abstraction. The theory usually comes later anyway—and it sticks better once you’ve wrestled with the mess. Reminds me of a book @Gigi once recommended: https://craftandvision.com/products/start-ugly