I think the quote meant that data design is super important and while it doesn't necessarily mean the codebase itself is pristine, it does mean that the codebase would be worse off without good data design.
The main thing is that, like you said, good data structures and relationships help with maintainabi…
I think the quote meant that data design is super important and while it doesn't necessarily mean the codebase itself is pristine, it does mean that the codebase would be worse off without good data design.
The main thing is that, like you said, good data structures and relationships help with maintainability. However, bad code is much much easier to fix compared to bad data design, usually because dependencies at that point are so deep-rooted that the migration to better designed data is painful.
I don't think you're wrong at all!
I think the quote meant that data design is super important and while it doesn't necessarily mean the codebase itself is pristine, it does mean that the codebase would be worse off without good data design.
The main thing is that, like you said, good data structures and relationships help with maintainability. However, bad code is much much easier to fix compared to bad data design, usually because dependencies at that point are so deep-rooted that the migration to better designed data is painful.