I can only conclude that PeeringDB is increasingly vibe coded (in the fullest meaning) because they keep releasing busted code that clearly has not been tested. Today they email me and a lot of other networks with a non sensical email that tells me to do something that does... nothing.

https://github.com/peeringdb/peeringdb/issues/1936

I can sometimes understand the desire to use AI tools, but seemingly none of this stuff is actually going through even basic testing in a staging environment, so frustrating for a service that absorbs quite a lot of sponsor money from orgs

@benjojo Hopefully they'll catch on that ad-hoc testing doesn't scale with such volume, and make test-driven development a hard requirement. If they don't sharpen that saw, the users will take the brunt of the testing burden.
@tychotithonus there isn't really volume though, the core database is like 100MB with indexes and the site has a pretty fixed number of features. It could be a checklist and a working staging environment, it doesn't seem that either of those exist
@benjojo So they're following the GitHub model then