When everyone is doing the fun work of chasing proofs of concepts, but leaving a trail of abandonware in their wake, no one is going to be interested in coming in to clean up the mess.

But hey, the highest time preference gets the funding.

Reply to this note

Please Login to reply.

Discussion

(A codebase with no tests is abandonware waiting to happen)

In the making - about to happen 🤣

This is probably my number one concern with nostr. Literally every client is riddled with very obvious bugs, but these devs seem to hit their vibe coding limits and quickly move on.

It's the industry standard. However, the market will prefer over the long run better-tested code than not. Bad code that survives is propped up by cartel mechanics (in our case, Nostr grants and no better options because good devs have other jobs).

I would fit in well among those who have complained about poor code quality since 1960.

i'm one of the few devs in nostr who also agrees there is a systemic problem with nostr's system of protocol definition, but protocols are my speciality, not UI

i'd love to build UI but it's a less efficient use of my existing skill set, i need a lot of practice to get good at GUI programming, and it's a big obstacle for me that i have to use sloppy languages like javascript and C++ to write UIs

Read this, then tried to "solidarity zap" you, but no go...😢

Wish I knew why my zaps fail so often...🤔

Minibits.

Have you done the update? Might help.

TY, but it tells me I'm running the latest?

Is it kidding me?🤔

Well, my Dear, thanks for the prompt...😳

As it turns out, apparently my Minibits version has been lying to me for a long time... I updated, lost access to all my sats, updated again over the air, and am stuck ATM until I get home and attempt a recovery from seed words...😜🤔🧐

That happened to me, and then I found out that I had written down the seed to the wrong wallet.

I was testing wallets, for a while, and always writing down the seed, and then I got a new cell phone...