nkcodes

Yeah, I'm going to try this out the coming weeks.

I wonder if there are people around who have stories to share about de-AI-Slopifying a codebase.

Yeah I feel like what you say makes sense. Part of my issue comes from the fact that we're a pre-PMF startup, so rapid experimentation and prototyping really matters at the moment with very little room left for deep thought around testing and benchmarking.

The trouble comes later when the "experimental features" actually start getting traction and we discover all the holes in our implementation.

By the time we need to "productionize" our experiment, it has already been patched all over the place to account for bugs.

I get a feeling that this is made worse by the fact that since a lot of what we're doing is rapid prototyping, our repo is cluttered with examples of bad code that the agent picks up on and then goes ahead to copy in its own implementation.

I get that we need to clean this up, but it's crazy trying to figure out where to start and what to tackle

I'm going to try out having product specs committed in the repo itself - hopefully this gives every agent I spin up context into how the product is supposed to behave as opposed to having to "guess" it from reading the code adjacent to whatever prompt I gave it