There are whole sections of code work that 4.7+ can't do simply because it is both over fit and stubborn.
God save you if you have a company with narrow but correct technical tradeoffs, because you operate at scale.
Opus from 4.7 one will wreck your code and argue for hours with your engineers.
Certain parts of our company have had to mandate 4.6 and a training doc to explain why our current choice is both the cost efficient and performant one and shouldn't just be ripped out.
Newer models will re-litigate the same bad, known failed architectures over and over again.
God save you if you have a company with narrow but correct technical tradeoffs, because you operate at scale.
Opus from 4.7 one will wreck your code and argue for hours with your engineers.
Certain parts of our company have had to mandate 4.6 and a training doc to explain why our current choice is both the cost efficient and performant one and shouldn't just be ripped out.
Newer models will re-litigate the same bad, known failed architectures over and over again.