[lqstuart]

I was in the “AI is grossly overhyped” camp because I work on large distributed deep learning training jobs and AI is indeed worthless for those, and will likely always be worthless since the APIs change constantly and the iteration loop is too cumbersome to constantly resubmit broken jobs to a training cluster.

Then I started working on some basic grpc/fullstack crap that I absolutely do not care about, at all, but needs to be done and uses internal frameworks that are not well documented, and now Claude is my best friend at work.

The best part is everyone else’s AI code still sucks, because they ask it to do stupid crap and don’t apply any critical thinking skills to it, so I just tell AI to re-do it but don’t fuck up the error handling and use constants instead of hardcoding strings like a middle schooler, and now I’m a 100x developer fearlessly leading the charge to usher in the AI era as I play the new No Man’s Sky update on my other PC and wait for whatever agent to finish crap.

[coffeebeqn]

Ah I see what my goal for this year is then. I have a large Steam backlog to work through. Unfortunately we currently code in short bursts and mostly are trying to figure out how these integrations are supposed to happen and why the different teams tell us different things

[g-mork]

this weirdly skirts my own experience yet somehow still read like sarcasm hehe. I think if we just return to calling it intelligent autocomplete expectations for productivity gain would be better established.

trying to hacksmash Claude into outputting something it simply can't just produces endless mess. or getting into a fight pointing out issues with what it's doing and it just piles on extra layer upon layer of gunk. but meanwhile if you ask it to boilerplate an entire SaaS around the hard part, it's done in about 15 seconds.

of course this says nothing about the costs of long term maintainability, and I think everyone by now recognises what that's going to look like

[lqstuart]

We just haven’t figured out how to use it. You wouldn’t try to create an entire project out of IDE templates, but how many “low code” attempts were there to do just that at some point?

I think there are phases in a project’s lifecycle where it’s more appropriate, at the very beginning and very late. I do not think junior developers should be using it, because it is much much harder to learn and it kills productivity having senior developers review 3000 lines of slop. Just stuff like that needs to be figured out.

[g-mork]

I've had some luck with this idea of keeping the "Clauded" bits separate where possible. Do you really care if it crates a spaghetti mess if the result is some visually beautiful low trust site that lives in its own repo entirely? vs. letting it run in autoapprove mode inside a module where critical hand-written crypto code exists