One way to solve that issue is to agree on the design pattern ahead of time before writing the code. Learning to think about the abstraction ahead of time is a

One way to solve that issue is to agree on the design pattern ahead of time before writing the code. Learning to think about the abstraction ahead of time is a powerful skill, but can be very uncomfortable to some people. There's a thing where we just allow people to say "I need to get my hands dirty, I can't effectively plan it ahead of time because I'll just end up changing my mind anyway," and nobody questions that reasoning or pushes back. The concept of "learning styles" has mostly been disproven. It's just a muscle you have to work, thinking about abstractions ahead of time without writing code. Writing helps a lot here. Anyway, if you're able to iterate on the design pattern before writing code, it can often only take a day or two, and then you don't have to spend another sprint re-writing the whole thing or whatever. Code reviews become a lot quicker/easier now as well, because you don't have to think about other design patterns while reviewing code, just the pattern already agreed on.