This week's question is from
Loopz:
How do you prioritize MVP features versus those for later, considering future data migrations and added overhead?
Learn by shipping; ship fast. It’s how me and my Indie friends like to develop.
This does mean we’re sometimes shipping features that could’ve been better prepared for the future. Data migrations can be painful and can add quite some overhead.
Yet, there are techniques to prevent this from happening. One is writing tests, which require structuring code to become testable in isolation. Isolation means flexibility and better preparation for the future.
Data migration is sometimes unavoidable; you don’t always know what to expect. However, by preventing unnecessary entity relationships and using data transfer objects (DTO), your codebase is more flexible for unforeseen future events.
Want to have your question answered next week? Ask your question on LinkedIn or Twitter.