Hacker News Reader

Comment by 0xy | Hacker News Reader

The cost of the next instance size on AWS is often 1/20th the cost of the developer time to make similar efficiency improvements.

View on HN

If you just use enough tape you can save money on all those pesky construction dudes.

If you just pull teeth instead of fixing them you need less dentists. Everybody wins.

Why bother with foundations if you can just tape together whatever works and call it a day? If it crashes you just add tape.

Welcome to the future.

> If you just use enough tape you can save money on all those pesky construction dudes.

But the comparison here is more like the other way around, isn't it? Fixing the problem by just throwing more resources at it is like making up for an inefficient construction workflow by hiring more construction dudes.

The "construction dudes" would be developers, not "compute".

Mike Judge was right!

Sometimes the slowness is due to using a distributed cloud architecture in the first place.

An increasing number of sites I interact with seem to love making me wait for API calls for everything. Like the lazy-loading is meant to improve the user experience, but if all I see is blurred placeholders and ...s while you make your six trillion cascading calls to your microservice architecture, I'd rather just go back to waiting for the full content to load in a few HTTP requests.

And then a team with the same mindset writes the software that runs on my desktop or phone or light bulb. From a certain point of view, that's even better, because someone else is stuck paying for the ‘next instance size’.

Reply on news.ycombinator.com