Maybe these are just my being petty, but my goal is to avoid them at all costs in my own work:

You can't trust code with no tests (almost all of Nostr).

You can't trust devs who look down on testing (almost all devs).

Putting devs on a pedestal encourages them to put their ego ahead of their users.

VC funding and grants are ensuring we only recreate fiat products but with Nostr events and zaps to attract new users.

AI generated code is generally unmaintainable and will rot with time. No one is going to come behind you up to clean up your messes, no matter how fun it is for you to make them.

We're not exactly early and on the frontier anymore. It's been 3 years and devs still act like children in a sandbox.

Web of Trust based on follow lists is too fragile to be effective.

It's not a feature, it's a bug.

"Go Fast and Break Things" will end up breaking Nostr and losing the trust of it's users.

Reply to this note

Please Login to reply.

Discussion

interesting. these all just sound like common sense.

I know right?

But I've been here for 2 years and haven't seen a whole lot of it. Just a clique of devs and their worshippers practicing FAFO and calling it building.

dont you think thats just immaturity though?

its very much a “im in my early 20s and my brain isn’t fully developed yet” bro kind of behavior

I think if you work with your head up in the clouds of pure software your whole career, you don't outgrow that. Like how fiat bankers and economists live in the fiat matrix where anything is possible if you just print more money, but with code.

My software experience was always tied to physical systems, so I didn't have that luxury. I had to make sure I didn't destroy critical industrial equipment with bad code, and that's pretty humbling.

Totally felt that. I'm from a critical systems background, including automotive, banking, and medical, and the widespread habit of delivering prototypes makes me want to claw my eyes out.

Everyone acts like it's funny or a joke. But it's not.

It leaves the impression that the protocol is bad, but it isn't.

even when i have already delivered the protocol as described and works with most clients for the relay side

it's so awful i need to clean it up and make a new thing

which is now officially past the beginnings as i have an openapi 3.1 UI and the essentials - publishing new events, and import/export of events

tomorrow i should have the filter done but i got mass and a philosophy discussion group to prep for and be part of

but yes... nostr protocol itself is practically still alpha, because it's stupidly messy and complicated, and even with all the things right the clients are working, not working, working, oh not working

yeah makes me want to claw my eyes out too

🫂

You have the absolute worst NIP, tho. The people implementing it barely understand what it's for.

i don't negotiate with communists, i just write good docs, a solid implementation that is hybrid with the standard protocol and it can do both things and then we just need a few client libraries

i can build WASM binaries for the web frontends also, and i have already got in mind building a simple event store that uses web browser storage, i'll just do a real simple thing along the lines of jumble and basta

Fascinating. I have known quite a few web devs in my life, and this rings really true to me. Modern SaaS doesn't give any shit about high quality software, only velocity.

I've had many occurances while working at SaaS that has made me feel like the people in that world are often disconnected from reality. So, you saying that about physical systems is very interesting to me.