I like the distinction between pioneer, settler, and city planner when thinking of the people working on new products. To me, it’s more about the lifecycle of a

I like the distinction between pioneer, settler, and city planner when thinking of the people working on new products. To me, it’s more about the lifecycle of a product as opposed to putting people into boxes. I feel like I know what business/code trade-offs I should make depending on which of those characters I’m currently playing. I also know what type of flexibility I should build into the product early on and which best practices can wait until market fit has been found. I wouldn’t want to take a city planner into the wilderness (sewers and squares before we know if anyone wants to even live here, lots of high quality code that has no users). And I also wouldn’t want to be a mayor having pioneers running my subway/water system (bandaid fixes, poor long-term decisions, spaghetti code) But I agree with you overall that people can adopt these roles based on context and aren’t limited by them