Personally I'd rather it over-engineer than under-engineer and leave gaps in the implementation that I'm unaware of. Not only does it make life easier to work w

Personally I'd rather it over-engineer than under-engineer and leave gaps in the implementation that I'm unaware of. Not only does it make life easier to work with the model this way, but over-engineering can be fixed later, as newer models are released, they will get better at cutting out the slop and refining the codebase. The only over-engineering I've really noticed is things like developing extra safeguards and extra tests, which is annoying but not a massive deal. Claude forgetting to implement edge cases I've specifically told it to cover is a big problem though.