Man, I disagree with all of this. The frontier models are actually good, and basically everyone in my F500 company has been using it. The codebases i work on are super-legacy java, where it does great despite us having like 75 different patterns for each task, and a massive front-end web repo where it thrives because we’ve been extremely strict in typing and patterns leading up to this. It even does pretty well across repo boundaries, despite having significantly lower context for those situations.
I genuinely will never understand the people saying they suck. Are the worth the price? I have no idea, I’ve never used them for personal project. But they are at least as good as a dev with 3-5 years of experience, at this point. Our career is boned.
I don’t doubt it’s possible to get better consistency but the juice is really not worth the squeeze for me. You end up churning through huge expensive models, orchestrating sub agents, writing out boilerplate hand-holding instructions (“please don’t break this, stop trying to commit to main, please lint ffs…”).
I don’t use it for Java but that would make sense with rigid enterprise patterns and VeryVerboseNamesThatAreEasierForAModelThanAHumanFactoryClazz {...
I don’t think our career is boned, moreso that all juniors trying to get in are boned. Everyone who knows what going on transition to a more hands-off architect role.
But like I said, our tokens are heavily subsidized right now. When they pull the rug, code monkey jobs will start to get listed again (with lower salaries of course).
Man, I disagree with all of this. The frontier models are actually good, and basically everyone in my F500 company has been using it. The codebases i work on are super-legacy java, where it does great despite us having like 75 different patterns for each task, and a massive front-end web repo where it thrives because we’ve been extremely strict in typing and patterns leading up to this. It even does pretty well across repo boundaries, despite having significantly lower context for those situations.
I genuinely will never understand the people saying they suck. Are the worth the price? I have no idea, I’ve never used them for personal project. But they are at least as good as a dev with 3-5 years of experience, at this point. Our career is boned.
I don’t doubt it’s possible to get better consistency but the juice is really not worth the squeeze for me. You end up churning through huge expensive models, orchestrating sub agents, writing out boilerplate hand-holding instructions (“please don’t break this, stop trying to commit to main, please lint ffs…”).
I don’t use it for Java but that would make sense with rigid enterprise patterns and
VeryVerboseNamesThatAreEasierForAModelThanAHumanFactoryClazz {...I don’t think our career is boned, moreso that all juniors trying to get in are boned. Everyone who knows what going on transition to a more hands-off architect role.
But like I said, our tokens are heavily subsidized right now. When they pull the rug, code monkey jobs will start to get listed again (with lower salaries of course).