← Back to context

Comment by gokulravi992

3 hours ago

The argument I'd make isn't about UI or features, it's about who owns security afterwards. The vendor has people whose whole job is patching things like this Ruby regex issue. The internal vibe-coded Jira usually has nobody, and the bugs that bite are boring ones, like a project page that loads for anyone who guesses the ID.

If they go ahead anyway, the ask is just that someone actually owns it after launch, not only builds it.