I've been hacking on gaffer (https://gaffer.sh) as a way to learn and explore agentic development. It's been fun and I've even picked up a couple customers.
As far as the "what to do with flaky tests", I error on the side of just outright killing the tests. Unless it's an absolutely crucial business case, I'd rather have no test than a test that slowly degrades trust.
For what it's worth, I've been working on a side-project to try to help with almost this exact situation and would be really interested if it could help you; https://gaffer.sh
I'm a solo dev working on Gaffer ( https://gaffer.sh ) - Centralized Test Reports for Teams and Agents. It's been a fun side-project test out vibe-coding and cloudflare infrastructure.
I think a lot of companies have some portion of their code that's been avoided for a variety of reasons. I think adding unit tests, simple automated tests and quick CI processes can really alleviate that fear...so eventually that section can be refactored (or moved to a service, etc).
I appreciate what you're saying about needed to be more deeply connected with the code for truly valid tests. What I'm wondering is if there's a happy middle ground where code shops just want basic coverage around their code.
Just a note; you SSL cert is either expired or invalid. So when I visit the link you posted, and get redirected to the https version, I'm greated with a big chrome warning page.
It's dramatically reduced the amount of annoying recruiter spam that I get. I'm proud that it was initially just a test-bed for new technologies, that actually became useful.
Looking for Javascript Developers (Node/Angular) with front-end development experience. We're trying to help developers get real information from recruiters.