Comment by a_bonobo
15 hours ago
It's honestly harder - you have to do a lot of extra work to ensure your work is traceable. It's super fast in doing things you have no overview of - it makes pretty figures, it runs command line jobs etc. and I'm sure there are mistakes in there. For now I'm pretending Claude Science is an IDE, like Positron/VSCode, and I have to keep enforcing proper git usage etc. so I can reproduce this work
Edit: compared to my tools before, it generally uses the same tools in the same way, just 20x faster than me and I mostly struggle to keep up and verify what it's doing
Sounds exactly like Claude Code (and ilk) tbh. Just a lot of the stakes are lower and a lot of people are more comfortable with it (e.g. there were always people blindly copying and lasting from StackOverflow) I suppose.
>copying and lasting
> have to keep enforcing proper git usage etc. so I can reproduce this work
Depending on what you mean here, it might be worth looking at jj, which works with git repositories. One of the features is that everything gets committed at change time (kind of) which may or may not be helpful to you here.
always add rules for it to never touch git besides git log. you do the commits. make reviews so much easier