Typically working with a junior on a project is slower than not working with them. It’s a little odd you see this as like that and that it’s also faster.
I just spent about a month using Claude 3.7 to write a new feature for a big OSS product. The change ended up being about 6k loc with about 14k of tests added to an existing codebase with an existing test framework for reference.
For context I’m a principal-level dev with ~15 years experience.
The key to making it work for me was treating it like a junior dev. That includes priming it (“accuracy is key here; we can’t swallow errors, we need to fail fast where anything could compromise it”) as well as making it explain itself, show architecture diagrams, and reason based on the results.
After every change there’s always a pass of “okay but you’re violating the layered architecture here; let’s refactor that; now tell me what the difference is between these two functions, and shouldn’t we just make the one call the other instead of duplicating? This class is doing too much, we need to decompose this interface.”
In my own personal experience it was actually kinda fun. I’d say it made me about twice as productive.
I would not have said this a month ago. Up until this project, I only had stupid experiences with AI (Gemini, GPT).
FarceOfWill@infosec.pub 1 week ago
Quik@infosec.pub 1 week ago
I don’t think it’s odd, because LLMs are just way faster than any junior (or senior) Dev. So it’s more like working with four junior devs but with the benefit of having tasks done sequentially without the additional overhead of having to give tasks to individual juniors and context switching to review their changes.
(Obviously, there are a whole lot of new pitfalls, but there a real benefits in some circumstances)
drspod@lemmy.ml 1 week ago
Link to the patch?
svtdragon@lemmy.world 1 week ago
The PR isn’t public yet (it’s in my fork) but even once I submit it upstream I don’t think I’m ready to out my real identity on Lemmy just yet.
pennomi@lemmy.world 1 week ago
Agreed. I use it in my daily workflow but you as the senior developer have to understand what can and cannot be delegated, and how to stop it from doing stupid things.
For instance when I work in computer vision or other math-heavy code, it’s basically useless.