Follow

One thing I'm learning about writing and maintaining a codebase that is now 12 years old is that it is a mistake to evolve one part of it to a new paradigm/architecture/framework/whatever and tell yourself you'll migrate the rest of it later, when you have to work on that part anyways.

Reasons:

- long time might go by before you do
- having different parts of your code on different generations is a huge barrier to making sweeping changes when you do need to do that.
- want to evolve again? Congrats you now have 3 generations in one codebase.

Lesson: take the time to go back and migrate the whole codebase soon after you have a new arch that you like.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!