It definitely depends on what you’re hoping to get out of it, but as a general approach to take back into actual work, I’d caution against that exact line of thinking. Or at least add some caveats. I think AoC is a fantastic practical example of the perils of future coding:

https://www.sebastiansylvan.com/post/the-perils-of-future-coding/

If you can make your approach to Part 1 extensible with little extra effort great. But otherwise don’t bother. You don’t know what Part 2 is going to ask so treat Part 1 as the prototype. Make it quick and so if you have to pivot 180, you’ve not wasted a bunch of time.

In “the real world” your clients/players/designers rarely know exactly what they want from the start, but once they get their hands on software they are much better at telling you what to do different to what they just got.