I don't get it either. I don't even commit changes until I know they work.
Discussion
I can see a bug occasionally getting past QC, but the bug just sitting there for weeks or even months?
That means nobody involved (and it's sometimes an entire team, and they're getting paid to build this stuff) has tried clicking on it... ever.
TBH sometimes devs have so much to do they are literally afraid to check prior work and find anything wrong because it will increase their stress and strain their deadlines 𫨠its literal anxiety
Then they need better project management. π€·ββοΈ
Software development has never not been stressful.
It's only stressful because they keep moving ahead when they still have bugs left behind.
Dragging entire cartloads of technical debt behind them and when you point to it they get pissed off because they're stressed out. But they don't want to stop because they get paid on delivery, not on quality. Because they people who are paying them actually don't care if the stuff works. π
But we can all see that nobody is using their app. We can't use it. It doesn't work.
I blame react βοΈ
A lot of Nostr devs use Svelte, it seems.
Then I blame JS in totality
I can agree with that.
Precisely. JS and all of its frameworks.
HTMX gives 95% of all the functionality of JS, 95% confusing bloated functions I no longer have to write. Just need JS for some animations and switches. And MOST of that is just animation...
I need to start looking into HTMX more seriously. While I'll talk crap, I feel like a JS is a necessary evil at this point, it's just a huge percentage of the job market now.
Clarify, TS specifically, I can't work with weakly typed languages, it just isn't for me. I started using PHP when they introduced strict typing semantics :)
HTMX.org
You must learn to handle everything server side. HATEOAS
Think differently. It weird at first, and the longer you've been using JS traditionally the harder it's going to be to re-wire your brain to program that way. It seems wrong at first but then the code base is so much smaller and less worry about how the client behaves because most compute is server side.
This is why Agile software development is a thing. It's saying "we'll get there when we get there, because we're doing it right." Deadlines are antithetical to Agile.
the hardest thing with deadlines and dev is that architecture is hard to measure without years of experience at actually implementing feature sets
very often marketing is in charge of feature sets and architects rapidly turn grey and drop dead of heart attacks by deadline
that is, if the architects are actually qualified, and IMO, software architects can only be called qualified after 10 years working as an engineer
there is no magic trick learning how to spec out a project without getting into overruns and quality problems due to deadlines and unrealistic expectations of management
Well, that's why architect is a real job. π€·ββοΈ
i'm getting close to being able to do it now, but i've been working mostly full time since 2018
nothing like failing to build the features you thought you could build to teach you prudence in architecture...
where building architects must learn to work with material and space, software it's about time and brains
It's like Product Owner and Business Analyst. Real roles that require competent, talented, experienced technicians, but usually end up filled with business people.
GM! πΈ π₯ :beetroot:
We've got that at my day job right now. The deadline is artificially imposed by the big trade show, the research and product teams take their time in figuring out what they want to debut at the trade show, they ask the devs to do it, the devs say "there's not enough time before the trade show," and chaos ensues. π
π
But I'm just one guy... Not a team.
But you at least asked other people to help you test stuff out and then tidy up before an official release.
They seem to just push this stuff out there, do a victory lap, collect some π½, and move on.
Shoot... I didn't even collect any π½
For critical nostr infrastructure no less...
Well nostr:nprofile1qqsw3mfhnrr0l6ll5zzsrtpeufckv2lazc8k3ru5c3wkjtv8vlwngkspypmhxue69uhky6t5vdhkjmndv9uxjmtpd35hxarn9ehkumrfdejj7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59u6hf4wa dropped me 2k sats but that's all. ππ» Appreciate you so much nostr:nprofile1qqsw3mfhnrr0l6ll5zzsrtpeufckv2lazc8k3ru5c3wkjtv8vlwngkspypmhxue69uhky6t5vdhkjmndv9uxjmtpd35hxarn9ehkumrfdejj7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59u6hf4wa
Hey I appreciate you too bro! Can I help do some testing still on grain? I was really busy when you DMd me before π
Please. I'm doing a bit of front end work to add the ability to import your notes from other relays. It works, but it needs improvement. I don't get a success result on large imports (it still imports them though) and my spinner works now, but doesn't go away when I get the result. I'm still kind of fresh with go and front end stuff. Other stuff to-do is in the issues on GitHub.
You should add paid services to your relay to help cover running costs. Maybe also set up a tip wallet.
nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t has a Geyser fund where we can accept sats for our work and distribute them to the team at intervals.
Don't ignore monetization just because you're early. It's easier to go from paid to free than the other way around.
I don't plan on running a public relay. I'll whitelist with my domain and certain pubkeys for my relay. I did think about applying for an open sats grant though.
And if I ever get around to it, I would run a public relay with configurations for cost per kind event insertion. 1 sat per kind 1, 10 sats per kind 3, 0... Etc. using lightning or eCash to top up credit, right through the frontend.
I love the idea of buying credits and tracking usage per npub, I think that's a good strategy. Keeps out the riff-raff π