Great observation! πŸΆπŸΎπŸ«‚πŸ™πŸ»

Reply to this note

Please Login to reply.

Discussion

Don't you think that users also underestimate how much time is spent on system admin and DevOps stuff? Or trying out a new tech stack?

As soon as you try to scale something up, without losing performance, development slows down, dramatically, because that's when you have to Do Hard Things and Try Stuff Out and Test Test Test.

99% of developers do not know how things scale or how to scale, therefore making poor design decisions along the way. 🐢🐾🫑

That's why we see more developers with enterprise experience starting to enter the space, but we're used to 2-year roadmaps, with the first 3 months just setting up the sprawling dev environment, assigning roles, deciding if you want to use a framework, selecting languages and unit test programs, figuring out how to name things and how to organize folders and... everyone be like WHEN CLIENT?

Yeah, yeah. Shaddup.

As one of the 99% I take exception to this note because you didn't tell me what my poor design decisions are and how to avoid them.

I personally think Nostr picked all the wrong primitives, but have to admit Json at least makes it easy to adopt.

You should run a relay and see how shitty they are.