I’ve never worked on a large(ten+ of devs including people that left) project that didn’t have flakes. They’re hard to fix. If you can’t reliably reproduce the

I’ve never worked on a large(ten+ of devs including people that left) project that didn’t have flakes. They’re hard to fix. If you can’t reliably reproduce then you don’t even know if you that it’s fixed or you’re just lucky. They’re hard to find. The change that they first appear tends not to be related to the cause. Leads to a lot of “not my problem” Really that’s just lack of ownership. Ultimately who owns the entire codebase. You say “my code” but I see a lot of people thinking that means the files I edit, not everything someone has to explicitly decide to spend day(s) fixing tests, and then only might fix a couple. The roi is super frustrating and it’s hard to spend whole days on a single test. There’s a ton of broken window theory. Once you get used to hitting rebuild, you just always hit rebuild and don’t even know it’s a new flake. The most effective thing I’ve seen when you hit this point is get all the test data, junit xml say, somewhere queryable and make graphs and explicit parts of okr with time against it.