it's easy to forget that whatever new that's added should be seamless
Yes, yes, yes. This is the major item that people forget when adding features or thinking about adding features. Most people seem to have the idea that it's just "okay it should work like this codecodecode done!"
If you do that, all that happens is your codebase slowly becomes a mess of non-integrated stuff that doesn't play well with itself, let alone anything else.
Integrating new functionality (and refactoring old functionality) so it plays well with absolutely everything else in the codebase is a lot of work, but it's absolutely necessary if you want your codebase to live for a long time.
no subject
Yes, yes, yes. This is the major item that people forget when adding features or thinking about adding features. Most people seem to have the idea that it's just "okay it should work like this codecodecode done!"
If you do that, all that happens is your codebase slowly becomes a mess of non-integrated stuff that doesn't play well with itself, let alone anything else.
Integrating new functionality (and refactoring old functionality) so it plays well with absolutely everything else in the codebase is a lot of work, but it's absolutely necessary if you want your codebase to live for a long time.