Idea Ripper // ArchiveCards: 1555 [Live] | Updated: 2026-10-14
Card #c864IR // #c864Synthesis

When you optimize, check the whole board, not just the square in front of you. A change that makes one person, team, or route better often makes the total worse. Optimize globally, then let the local wins follow.

— In our words · Source: Algorithms Every Programmer Should Know (Aniket Wattamwar)

[Use when]

A team is optimizing its own piece while the total keeps getting worse, or you are tempted to grab the obvious quick win.

[Why it matters]

The greedy mistake is optimizing one item locally and making the overall system worse.

More from Algorithms Every Programmer Should Know

#c858Before you chase "better," name what you are giving up to get it. Speed costs money. Thoroughness costs time. Reach costs attention.…You are deciding between two "better" options and keep assuming one is best in every way, or someone promises… #c859When you plan a system, a launch, or a budget, design for the worst realistic case, because that is exactly where things break. The average…You are sizing a plan, a budget, or a capacity and someone says "on average it will be fine." #c860Do the crude version first, the one that just works, then improve it once you can see the real bottleneck. Optimizing before you have a…You are stuck planning the perfect approach, or someone wants to optimize a process that does not work yet.