Interesting article but the author seems trapped in an antiquated “compute time is more expensive than developer time” mindset. For most startups today the EC2 budget is negligible compared to the dev team budget. If you’re successful enough that the compute cost matters that’s a good thing and you can deal with it then.
Optimizing for problems you don’t yet have just keeps you from launching and getting successful enough to actually care about your compute costs.
Optimizing for problems you don’t yet have just keeps you from launching and getting successful enough to actually care about your compute costs.