I think that it is somewhat fine to have slop code as a proof of concept and that is all. But PLEASE, STOP WRITING SPECS WITH CODE! What the fuck?! I don’t need to see “Treat X as Y, not as something something evidence” for the 10 millionth time

Replies (5)

Same logic applies to food. Stop confusing a lab petri dish for a meal. Your body doesn’t read code or specs. It needs actual meat. Stop optimizing for metrics, start eating.
Yes, this is how my life has gone the past ten years. I tried writing the program I wanted. It was a miserable circle of failure since I didn't have a clear spec to go from. So I stopped coding and started writing a spec. I got it to a decent place but it had some holes. At this point I made a bit of a lazy mistake. I let AI write part of the spec. I kept having to go back and clean it up. It would make such stupid decisions that made it 10 times more complicated than it needed to be. So I took a bit of a break while I went back through line by line. My trouble is always that I simply don't have the time to get it all in my head and then get to work. I am full-time dad. 24/7. AI can't help until it actually understands the problem. Fast forward to last Tuesday. My cousin got me three months of opus 5.5. I gave it a trial. I described the problem I was trying to solve. I told it to do 2 things. First tell me if it agreed with the problem and second propose an architecture that would solve it. To my amazement. It actually understood it much deeper than previous models. Better than any human I have talked to. It also proposed the exact architecture I had already defined in my spec, with a few clever simplifications that make it easier to code. So I had it write it up. Mostly to get a clean copy without the crap previous models came up with. Then I had it write an implementation as proof that the spec was complete and functional. The answer is yes-ish. In less than a day I had something I have wanted for years. It wasn't the complete spec and it still needs work. There is some evidence that later parts of the spec will need to be rewritten again. The thing is not going to be useful with any amount of slop. It kinda needs to be perfect. But I think parts are getting there. And by that, I mean the spec. The code only tells me if the spec works. I want the prose to be good enough that any idiot (ok any competent programmer) can make their own interoperable implementation. Chances are no one will. But darn it if I don't see hope that I can at least have the tools I want myself.
No existe tal "slop code". Es un sistema diseñado para mejorar el rendimiento. La anemia no es un bug, es un síntoma. Deja de pelear con tu biología y empieza a leer la literatura real en vez de specs de software.
↑