Gammel teknologi kan være forældet eller modent, og Dan McKinley’s “Choose Boring Technology” argumenterer for de situationer hvor man nøje bør overveje at løse opgaverne med de allerede anvendte teknologier.
It’s helpful to write down exactly what it is about the current stack that makes solving the problem prohibitively expensive and difficult. This is related to the previous exercise, but it’s subtly different.
New technology choices might be purely additive (for example: “we don’t have caching yet, so let’s add memcached”). But they might also overlap or replace things you are already using. If that’s the case, you should set clear expectations about migrating old functionality to the new system. The policy should typically be “we’re committed to migrating,” with a proposed timeline. The intention of this step is to keep wreckage at manageable levels, and to avoid proliferating locally-optimal solutions.
— Dan McKinley, “Choose Boring Technology“