Once you've seen enough code, the right abstraction becomes easier to spot. Applications are more similar than they are different. That's why we have the conc

Once you've seen enough code, the right abstraction becomes easier to spot. Applications are more similar than they are different. That's why we have the concept of design patterns since these occur with enough frequency that we should just give the abstraction a name instead of re-inventing it each time. Problem today -- my observation -- is that many younger devs don't ever bother learning design patterns so we end up with 1) devs who aren't aware of common, existing patterns codified decades ago and then 2) think that the "wrong abstraction" is expensive partially because of a lack of knowledge of the "right abstraction" to use.