2 ms·
Everyone is “overspending” on infrastructure. There is always money to save the question comes down to where you want to expend your engineering effort and wha
by colechristensen 4y ago
Everyone is “overspending” on infrastructure. There is always money to save the question comes down to where you want to expend your engineering effort and what risk levels you want to take.
“Make fewer features, focus on spending less” is a valid executive decision, it’s just a matter of priority. Twitter seemingly being feature complete and losing lots of money most years makes doing this now a decent decision.
Spending too much like that is generally a symptom of not paying attention and noticing the waste, it happens from time to time. Gets to feel normal, then you notice and correct.
I’ve been mostly responsible for cloud spend a number of times and had several events of cutting spending by 20% or more over the years.
- bagels 4y agoI've had the same experience at startups. Usually it's time to make features, but eventually the spend gets high enough to justify spending a couple weeks of engineer time on it to cut out waste. Same thing happened when I worked a large internet company, just on a different scale.