aint being the scapegoat exactly how you protect prod?

If they expect you to write or go through 1000s of lines of code in a single day. your whole job isn't programming, is to be the scapegoat.

I spent like an hour yesterday bullying Claude out of using a ResizeObserver, Refs and a useEffect construct just to fix the height of a container (there was a bug where the container didn't properly scale down in height because some weird hard-coded properties in an external component inside of it). I knew that it had to be solvable with just the right css selector, but I was lazy and didn't want to manually go through the html and figure out which selector on which component would be the right one. And on paper "Go through this massive block of html and check which property is out of place" should be the kind of use case where LLMs actually work. The stupid thing introduced two new different catastrophic failure modes where the entire browser crashed due to excessive rerenders before it found something that even remotely worked. And then I had to spend another hour stripping out unnecessary style properties it glued on while looking for a working solution. In the end, I probably would have been much faster doing it by hand.

Yea if you don't explicitly give it direction on how to keep the code maintainable, it will gladly just spew shit into the same file until you have 10K LOC in it.