Skip to content

Programming Quote by Anonymous

“With a monolithic project, late in the game, we can’t even do much to cut costs. We have already written requirements for things we’ll never get. We’ve designed, and even written code for things that we’ll never complete. All that work is wasted. If only we had known the truth. We could have…” quote by Anonymous
Download Open image
““With a monolithic project, late in the game, we can’t even do much to cut costs. We have already written requirements for things we’ll never get. We’ve designed, and even written code for things that we’ll never complete. All that work is wasted. If only we had known the truth. We could have deferred some of that work. We laid out this project with an all-or-nothing mentality. We analyzed it all. We designed it all. We tried to code it all. We discovered, too late, that we can’t have it all.””

Anonymous

About This Quote

Source Speech: Project Management Retrospective, unknown source

A large, monolithic project leads to wasted effort when requirements change late, causing over‑design and unused code.

In simple terms: Late changes make big projects wasteful.

Key Takeaway

Plan flexibly and prioritize essential work.

Themes

project management risk scope efficiency

Mood

reflective cautious

Type

advisory analytical

When to use this quote

  • software development
  • product planning
  • budget reviews
  • stakeholder meetings

Key Concepts

lean development scope creep cost control

Questions to Reflect On

  • How could early iteration have reduced waste?
  • What criteria decide what is essential?
A Different Perspective

Over‑engineering can still happen despite early warnings.

4.8 out of 5 (4 ratings)

More by Anonymous

Explore all 163,108 Anonymous quotes

More Programming quotes

Browse all 6,478 Programming quotes