India landed Chandrayaan-3 near the lunar south pole this fortnight, a place no one had reached, on a budget of about seventy-five million dollars, less than many films spend pretending to go to space, and the reflexive framing in much of the coverage was that the achievement was impressive because it was cheap, as though cheapness were a charming handicap the Indians had overcome rather than, as I want to argue, a substantial part of how they succeeded. I build things under constraints for a living, and I want to defend frugality, real frugality, not corner-cutting, as an engineering virtue in its own right, and to argue that the hard budget was not the obstacle to the achievement but, in a way the well-funded rarely understand, its engine.
There is a law of systems design, half-joking and entirely true, named after John Gall: a complex system that works is invariably found to have evolved from a simple system that worked, and a complex system designed from scratch never works and cannot be made to work; you have to start over with a working simple system. Frugality enforces Gall's law by brute economic necessity. When you cannot afford the elaborate, the redundant, the gold-plated, you are forced to build the simplest thing that could possibly work, to understand it completely because you cannot afford to paper over your incomprehension with expensive margin, and to add complexity only where you have proven you need it, because every gram and every dollar is contested. Abundance permits the opposite discipline, or rather the absence of discipline: it lets you buy your way past problems you do not understand, wrap every uncertainty in expensive redundancy, and accumulate complexity you cannot fully model because you could afford to add it. The economist E. F. Schumacher argued half a century ago, against the whole grain of his profession, that bigger and more expensive is not the same as better, and that there is a wisdom in appropriate scale and deliberate limitation that the cult of growth had trained us to despise. Chandrayaan is Schumacher vindicated in orbit: a program that could not afford excess and therefore built something lean, comprehensible, and robust, and got it to the Moon.
The counterargument is serious and I will not dismiss it, because "cheap" is genuinely sometimes a euphemism for "fragile," and I have seen budgets used to justify the omission of things that were not excess at all but essential margin. Well-funded engineering can afford proper testing, real redundancy, the failure analysis and the spare capacity that keep systems alive when reality exceeds the nominal case, and there is a long graveyard of cheap projects that failed precisely because they economised on the margins that turned out to matter, so that frugality shaded into recklessness and the saving bought a catastrophe. This is true, and it means my defence of frugality is not a defence of minimising cost, which is a different and often disastrous thing. The distinction, and it is the whole of the argument, is between frugality as the discipline of spending only on what matters and understanding exactly why, and mere cheapness as the reflex of spending as little as possible regardless of what it costs you in fragility. Chandrayaan was the first. It was not underfunded relative to its actual needs; it was disciplined relative to its needs, ruthlessly clear about where a dollar bought real robustness and where it bought only the appearance of seriousness, and India had, in earlier failures, learned precisely that distinction at real cost.
Because that is the part the "impressively cheap" framing misses entirely: the frugality was not despite sophistication but a form of it. It is far harder to build the lean thing than the expensive one, because the lean thing requires that you actually understand your problem well enough to know what you can safely leave out, and understanding what you can leave out is a much deeper competence than being able to afford to leave nothing out. Anyone with a large enough budget can throw redundancy at uncertainty; it takes real mastery to know which uncertainties genuinely require the redundancy and which are being insured against out of ignorance and fear. The organisation that has been forced, by a hard budget and by earlier honest failures, to develop that discriminating knowledge ends up not merely cheaper but often genuinely more robust, because it has eliminated the fragility that hides inside unnecessary complexity, the failure modes that live in the parts you added because you could and never fully understood.
So I read Chandrayaan not as a triumph of thrift over quality but as evidence that the two were never opposites, and that our reflexive equation of expense with excellence is a kind of decadence, the mental habit of people who have never had to know the difference between what matters and what merely reassures. The discipline of enough, of building exactly what the problem requires and understanding every part of it because you could not afford not to, is a higher engineering virtue than the capacity to spend without limit, and it produces, more often than the wealthy like to admit, the better machine. India did not reach the Moon in spite of having little. It reached the Moon, in part, because having little forced it to know exactly what it was doing, and knowing exactly what you are doing is, in the end, the whole of the craft.