What makes a good software architecture?

We keep hearing "signals are bad", "clean architecture is the answer", "ports and adapters is the way". But do these technical choices actually determine whether a codebase stays maintainable? I've seen well-structured projects rot and messy projects thrive. Let's discuss what actually makes codebases messy over time - and whether architecture patterns matter as much as we think.