Where do you develop that kind of intuition around how to design a system that can satisfy today's requirements and be open for the future?

Yeah, I think this is one of those things where judgment really comes from lived experience.

when you see a feature land in a way that's a little bit different than the way that you originally intended for it to land, or if a feature gets unshifted or if it becomes deprecated, or if a new feature becomes the better way to handle something at a product level even, if a new kind of market emerges.

that makes your existing product no longer as relevant and your team actually has to fully pivot into a completely different domain.

I think seeing the ways that what is relevant for your customer can change is what ultimately gives you that intuition for how your systems need to evolve.

And I would also say it really depends on the life cycle that you're in, like the stage of the life cycle that you are in when you're building something.

For example, when you're in very, very early phases of prototyping, this is actually one of the things that I think AI is the best at.

How do I get that incentive in the right place so that, um, I can get the thing I have ownership on, uh, finished?