because the tooling is struggling to catch up and adapt. there's still no vetted all-in-one solution that does code review, charts quality metrics, ingests incidents, and writes tests. there could be but each solution would necessarily need to be so bespoke to a codebase that you might as well hire some AI-pilled QAs and come up with it yourself (which is my current job, more or less)

smarter companies are coming up with internal tools that dogfoods on itself which means vendors can't match specificity. but those are the companies where the CTO codes and contributes regularly, and are able to pull the strings across the company to get something like that running

I compare that to the last place I worked where the CTO hadn't coded in decades and was throwing spaghetti at the wall trying to figure out how to use AI. this meant we had designers/PMs shipping directly to prod and but for the sake of a very stressed out Staff Eng and I, they would've force pushed everything with zero testing. but even still, there were TPMs building out a central TPM dashboard to help with cross-team collaboration. and that was largely because their director was very good about getting all of TPM to buy-in, set up their specific configs, and adopt consistent roadmap templates

it all depends on if your leaders actually know what to do with AI or if they listen to some dumbass podcast by a barely-know-anything influencer to drive how they approach things and are looking for hail mary throws