Nostr Archives

how does this get through QA? are you guys dogfooding it? @75d737c3…c07efaf7 📝 40e1814a…

💬 15 replies

Replies (15)

It's still in early development, we noticed a bunch of issues and we know there's many improvements still to be made. Even with that being the case, the last release is better than the one before it, so there's no harm in releasing. Next release will be better than the current one for sure. Perfect? Of course not, nothing is. But consistent continous improvements beats "not-releasing because there's bugs" in the long run.

0000 sats

verbiricha7d ago

I'm not asking for perfect, every software has flaws and improves over time and I'm cheering for you. But this is something so fundamental and the fact it's badly broken is not a good look at all, specially when we are talking about something as sensitive as e2e encrypted comms. That's why I asked if you are dogfooding it. Smol demos with fresh npubs don't count. Simulated environments that don't look like real world production usage doesn't count either. I'm talking about using it on a daily basis, using it for all your team's comms until you nail down the onboarding & basics and squash all the obvious bugs, then build from there.

000

Niel Liesmons7d ago

Meanwhile, me dogfooding my own task, spec and project management, in da app:

0000 sats

Danny, the cyber guy7d ago

We're working really hard on getting it to a better state! The plans are bigger than you can imagine 🦫, but they take time

0000 sats

Max7d ago

What's QA?

0000 sats

Troy7d ago

Releasing critical defects that cause 100% breakage for a significant segment of users is far worse than holding back until those defects are fixed. The "release early and release often, even if it's dogshit" has never been a good paradigm. Give weight to defect classifications, keep track of your weighted defect count prior to release, then go into "no new features" mode until the score is low enough AND there are no critical high-priority defects. It's not even challenging to do. It just takes being patient while being excited to release new features. The other option is to have a reputation for releasing garbage, which results in new people not even installing to check it out. Or worse, dedicated users swearing to never install software you make ever again. That's how Norton Utilities went from being the de-facto software for all admins in the PC world, to total bankruptcy.

0000 sats

Niel Liesmons7d ago

:110percent:

0000 sats

il_lost_7d ago

What kind are you using for task? Is regular event

0000 sats

Niel Liesmons7d ago

https://www.chateau.community/communities?c=npub1vcxcc7r9…

0000 sats

il_lost_7d ago

I'm trying to use 2323 for todo/done and the replica goes as update and 2424 wish (root) and (replica) possible. Since I was there I used bookmark, because it already had the default to add events and so I created two lists, one Todo and the other Done, so if the card exists in the two lists it is completed I will try to understand where the two can find reconciliation

0000 sats

Niel Liesmons7d ago

@verbiricha advised me on that Easter egg kind number btw :PepeLaugh:

0000 sats

JOE2o7d ago

I think it's not so much that, it's more a fundamental cake and eat it to situation with regard to what is actually being attempted here. You cannot have stateful and stateless at once, managed and unmanaged, and if you try then every release will have a critical issue, you're simply shifting critical issues around.

0000 sats