Nostr View

The Bug Acceptance Committee is out protocol-thumping, again. Please remember: *They are preaching the Gospel of Buggy Software instead of fixing the bugs.* Do not let them gaslight you. Demand better quality. Nostriches aren't second-class Internet citizens. You deserve BETTER software, than the legacy crap, not worse software.

Silberengel @Silberengel - 1d

I have no idea, but they're the loudest faction on here and their rhetoric is the reason why nothing broken gets fixed.

mleku @mleku - 1d

"it works on my side" is their main slogan

Silberengel @Silberengel - 1d

They just push new bugs onto their old bugs, basically.

Silberengel @Silberengel - 1d

Yeah, incompetence is more likely than malice.

Silberengel @Silberengel - 1d

If only. I don't think they even test it on their own side.

Silberengel @Silberengel - 1d

They don't have manual testers and they don't deliver their code bundled with unit tests or containers. And they release, and stuff that used to work is broken (regression, very bad), and the new stuff doesn't work and sometimes the build is missing files or is corrupted, and can't be installed. They're testing nothing, methinks. They don't even try installing it on a different system, running it, and clicking around a bit. Otherwise, they would quickly notice the integration problems. You're supposed to _at least_ do that, before a beta release announcement. Take those 15 minutes, please.

mleku @mleku - 1d

Hanlon's Razor but you should never discount a deeper level of malice that involves the erring person to be acting out the will of one (s) who are malicious and manipulated the very way of thinking that led to this error (promoting error is my personal concise definition of evil)

mleku @mleku - 1d

*grumpy dev veteran yells at brick wall*

mleku @mleku - 1d

Silberengel @Silberengel - 1d

😅🤙

mleku @mleku - 1d

Silberengel @Silberengel - 1d

That's why I'm attacking the rhetoric, not the people. The devs are hearing this "don't test, don't fix, fuck the users" rhetoric all day, every day. They should know that this is not a Natural Law. Nostr products CAN be good. Nostr products SHOULD be good. No more excuses, no more spin. Let's just fix the processes and the bugs and develop like adults.

Silberengel @Silberengel - 1d

😅 Seriously. Next phase is banging your head against the wall in frustration.

mleku @mleku - 1d

nah, next phase is building a killdozer

Silberengel @Silberengel - 1d

Well, we're the killdozer. We can just develop a Nostr Stable Version edition of all major use cases and the users will wander over, eventually, when they've had enough of the bugs.

Silberengel @Silberengel - 1d

😅

mleku @mleku - 1d

making life easier for devs so bugs are easier to avoid is also part of the work... something i'm very passionate about i have an allergy to complexity, everywhere i see it i try to expel it

Silberengel @Silberengel - 1d

That requires architectural work, but they don't want to do that, either.

mleku @mleku - 1d

Domain Driven Design is one good discipline, i also found another one that is quite useful that nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z talks about a lot, Behaviour Driven Design at my paid gig the guys who are building the back-end/middleware of our application use both of these techniques in their work also... i honestly haven't studied them hard enough, but i grasp the basic principles reasonably well DDD is kinda like an elaboration of the Single Responsibility Principle and aims to help meld the expertise of subject matter specialists who have got less software engineering skills with the programmers, project management and ops people

mleku @mleku - 1d

big ball of mud is the name of their game

Silberengel @Silberengel - 1d

The reason I call it "the Bug Acceptance Committee" is because they regularly demand public confessions of adherance. It's like some sort of struggle session, where the trending list fills up with note after note of VIPs declaring that WE LOVE THE BUGS. WE ARE ONE WITH THE BUGS. BUGS ARE BEAUTIFUL. WE ACCEPT THE BUGS. PEOPLE WHO CRITICIZE THE BUGS ARE AGAINST US. And their threads then fill up with people hugging them. Oh, yes, we all love the bugs. Oh, yes, we all accept the bugs. Without the bugs, we would be *gasp, horror* X. Creeps me the fuck out and is complete nonsense. Yo, bro, the bug in your code is on line 429 in file "relaysort.ts". You have a typo. 🙄 Just fix it. WTF the actual fuck is your problem?

Silberengel @Silberengel - 1d

WHY DON'T THEY JUST FIX THE BUGS? ASKING FOR A FRIEND.

Silberengel @Silberengel - 1d

😅

Silberengel @Silberengel - 1d

Yeah, I'm big on BDD. I'm doing it at my day job, as well, and already uncovered some major errors in the spec.

mleku @mleku - 1d

benchmarks? i am just talking about how the Go language makes it easier to throw stuff out fast... it doesn't really force you into good architecture, i think that some aspect of why OOP languages are so wordy is they are trying to do that but it's the wrong place for it go is unfortunately a poor choice for doing UI tho... there is numerous projects out there but all of them fall down in really big ways... the best one for performance the problem is the devs have architected it wrong... which is my point about how the language itself can do little to stop you making bad designs... i do think that "internal" and "encapsulated" (non-exported) symbols can complicate extensibility a lot but the old days of C++ and now Rust "sAfEtY" which is just a dogwhistle for "you are superior and everyone else is retarded and needs to have guard rails on everything or they will breach your interfaces and abuse your code" yeah, that's usually because they have created a bad architecture btw

mleku @mleku - 1d

have you had a chance to have a look at my proposal for decomposing the query interface btw?

Silberengel @Silberengel - 1d

@ me on Matrix, with the appropriate thread. Went down in the chatter.

Silberengel @Silberengel - 1d

😅

Showing page 1 of 2 pages