Megabank's platform team forced every developer onto one stack — and nothing shipped for a year

Do Repeat Yourself

Megabank's platform team forced every developer onto one stack — and nothing shipped for a year

A new senior VP at Megabank decides three teams building similar account, investment, and credit-card portals are wasting effort, so he creates a platform team to mandate a single Go/React/Kubernetes stack and shared components. The investment team needs Erlang for fast market data; the credit-card team finds Go overkill. Shared components lack needed features, documentation stalls, and no team ships that year — though the VP's bonus is fine. The lesson: allow repetition and set clear boundaries instead.

Minimizing the amount of code written or the number of technologies used isn’t a goal in itself - but building good products, shipping them on time, and allowing teams to work effectively together is.
  1. pmg101

    Sometimes syntactic duplication can give you a hint to underlying semantic duplication. But it's no more than a hint.

    DRY doesn't mean don't repeat a similar looking block of code, it means try to structure your code so that each element of the design has a single representation.

    There's no shortcut to good design where no thinking is required, much as a lot of people seem to wish there were.

  2. kstenerud

    I was with them right up until the admonition against standardizing the UI components. This is not an all-or-nothing proposition. You build a standardized library incrementally, and you slowly migrate codebases over to use them. I've seen some pretty horrendous UI mish-mash in what should appear to be a single application, because each piece was done independently and then stitched together.

    You end up with drifting implementations that may or may not come from the same root at different points, where the same fix has to be applied multiple times as each team learns the lessons for what not to do, etc. Effectively what DRY is about.

  3. umvi

    Or as the go proverb goes "a little copying is better than a little dependency" (https://go-proverbs.github.io/)

  4. jedbrooke

    reminds me of WET: Write Everything Twice. Instead of immediately jumping to DRY, actually write out the two similar tools, then see what actually makes sense to combine into a shared dependency.

  5. drunkboxer

    I've always found DRY to be more useful when applied to data rather than code. Eg don't have two versions of an enum, or a mapping, or the information in some database.

More from this day

2026-11-17