They must’ve realized Mythos couldn’t live up to the hype, rebranded it Opus 4.8, and will come up with some bs about sparing humanity from collapse by keeping it out of your enemies hands.
Holy shit, you go to add a feature or refactor a vibe-coded system and you end up changing everything.
You either gotta go all-in and vibe everything so you don't have to see the maintenance cost, or you gotta be very careful with what generated code you're accepting.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
My hope is that there is a large enough group of young, ambitious engineers that will take it upon themselves to relearn system design and correct the slopification of actual important software.
And I hope their management, their team, and their company lets them.