Even if the code has been absolutely perfect at the time of writing, growth of the codebase, and changing requirements could make it bad. e.g. if you have 10 i

Even if the code has been absolutely perfect at the time of writing, growth of the codebase, and changing requirements could make it bad. e.g. if you have 10 items to store, then a simple file may be a pragmatic choice. When it grows to 10,000 items you may need a database. But if you started with a database for just 10 items, people would complain it's overengineered. If you have 2 classes, an if/else can do, but at 20 you need some Factory pattern, which would be an architecture astronautics if done from the start. And when you try to anticipate such growth, you'll create overcomplicated code whenever you guess wrong. A continuously developed project will systematically keep outgrowing itself.