Why is premature optimization discouraged in code standards?

• A. It guarantees faster code.
• B. Premature optimization saves time in the long run.
• C. Concentrating on readability before performance.
• D. It can complicate design and may not yield benefits.

Answer: (D)

Premature optimization is about speeding up code before you have evidence that speed is even a problem. The main lesson is to keep design simple and maintainable first, and only optimize where profiling shows a real bottleneck. When you try to optimize too early, you add extra code paths, clever tricks, and special cases that lock in architectural decisions and make the code harder to read and modify. Those changes often don’t pay off—performance gains can be small, or the bottleneck shifts after you refactor, so the effort spent on premature tweaks ends up wasted. The best approach is to write clear, correct, maintainable code and then measure performance later, targeting actual hotspots for optimization.