My time is more valuable that I will use a model that doesn’t f** up my code base.
I mentioned here (https://news.ycombinator.com/item?id=48766275) how poorly it handles my specific use cases. My coworkers in DevOps and frontend UI swear by its cost-effectiveness, whereas I strongly prefer the reasoning capabilities of Opus 4.8 and Fable 5.
Composer 2.5 seems to be SOTA for Helm charts and React/Vue, but, for my usecases it absolutely struggles spectacularly when tasked with rigid body dynamics or kinematic logic.
If you listed it, how many features/LOC or vice-versa? Really hard to know if 200K LOC is good or bad, at the surface it sounds like too much, but I don't know what the application was either.
If I had to give advice I’d say to just do it. Work on some project that interests you and go for it