There's only one thing you REALLY need to discover in review... is there a glaring vulnerability?
Everything else can come out during iteration with real usage and users
Any sooner is premature optimisation and distraction
maybe a hot take but i now consider adversarial reviews mostly a waste of tokens. far better to use those tokens on empirical combined with formal verification. i have updated pstack to use the interrogate skill less, and eventually i think i may remove it altogether
i have
Ok, so Play Store has rejected open testing due to the site's terms and conditions not meeting their expectations
But a PR is in that attempts to address it, so hopefully that gets merged and I'll kick off another review as soon as it is
github.com/dev-null-sh/de…
Take note if
