Definition
Good enough software is the idea that quality is a deliberate decision, not an absolute to chase forever. Software is good enough when it meets the genuine needs of its users and stakeholders within the constraints of time, budget, and scope that the situation imposes.
The Pragmatic Programmer authors are careful here: good enough does not mean sloppy or buggy. It means consciously deciding how good is good enough for this purpose and stopping at that line rather than gold-plating.
Why it matters
How it works
The practice is to involve users in the quality tradeoff. Often they would rather have a working system today with a known limitation than a flawless one next quarter. Treating scope and quality as something to discuss, rather than something the developer decides alone, keeps effort aligned with real value.
The Pragmatic Programmer authors also advise knowing when to stop. A program, like a painting, can be ruined by overworking. The discipline is to deliver when the software genuinely serves its purpose, while never confusing a conscious good-enough decision with the neglected decay of a broken window.