It's like owning your 10th or 15th laptop when many are on their 3rd to 6th.
The latter are happy with a new laptop, where as the former understand they just bought the death of their laptop the first day they take ownership of a new one.
Dealing with "cruft" is the future of any project with longevity.
Likewise, working on a codebase with a mindset of having a relationship with it for 5-10 years potentially is something there isn't enough thought conversation about clever architecture often outliving clever coding/tech/stacks.
> Likewise, working on a codebase with a mindset of having a relationship with it for 5-10 years potentially is something there isn't enough thought conversation about clever architecture often outliving clever coding/tech/stacks.
If you are referring to B2C startups, that is because users are far more valuable than code.
I wasn't referring to B2C Startups, but agree with you that users are far more valuable than code, but maintaining and refactoring said code can take away from delivering value to the users, and instead more attention can be spent on the the developers.
The latter are happy with a new laptop, where as the former understand they just bought the death of their laptop the first day they take ownership of a new one.
Dealing with "cruft" is the future of any project with longevity.
Likewise, working on a codebase with a mindset of having a relationship with it for 5-10 years potentially is something there isn't enough thought conversation about clever architecture often outliving clever coding/tech/stacks.