Retrofuturism as others have said, but probably more specifically cassette-futurism

A [*squints*] ~20 gun frigate with a crew of only 30-50? That’s sounds like a startup nightmare. You’d probably want double that to be comfortable.

“Get in on the ground floor of our fast paced, dynamic environment! Must be self starter willing to work watch-on-watch for the team. No sick days.”

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).

Things I’ve realized while working with AI (Claude code):

• It’s fantastic for very small macros and medium length scripts. Think dev ops stuff, pre-commit hooks, transforming data. Keep it small enough to manually review and something you can run without destroying anything important. This can massively boost your codebase QoL. [Double bonus for not wasting tokens to solve the same problem over and over]
• It’s decent-to-good at debugging but not consistent with fixes. It can find some utf encoding edge case that might have taken you 1hr+ but suggest the dumbest bandaid fix you’ve ever seen. Also very good at spinning up unit test suites for basic edge cases.
• Due to obvious training bias, it’s pretty good with common libraries and cloud platform infrastructure. It could probably help with writing a complex cron call, debugging regex or fixing an IaC config. On the flip side it won’t bother to use the latest package version or know your niche/new library.
• It does better with greenfield because exploring your codebase introduces a ton of bias. It might try to fit in an ugly hack when a refactor to simplify everything is way easier.
• It’s absolutely garbage with UI, just throws the most disorganized HTML together that isn’t reactive or reusable. OK enough for ugly internal stuff but God help anyone relying on it for that.
• This is setting up to be the biggest rug pull in history. People that buy into it heavily just to save a couple bucks on engineer payroll are going to be fucked when they start ratcheting up the token price.

All in all it can be useful when used with care but will never be a magic bullet.