3 ms·
At $large-scale company this happens pretty regularly if you just look for expensive things and ask: * "Can I just remove or slowly deprecate this?" I.e this
by siliconc0w 3y ago
At $large-scale company this happens pretty regularly if you just look for expensive things and ask:
* "Can I just remove or slowly deprecate this?" I.e this job generates data no one uses, or alerts people just bin-bucket or has been already replaced by faster/ better.
* "Can I cache this?"
* "Can I run this at a lower-priority/off-peak/less available?"
* "Can I reduce the frequency or move processing to deltas?"
This is just the easy stuff you can usually do in a few lines of change without even getting into basic optimization rewrites. Most internal things at $large-co are built because someone thought they might be useful, they might get promoted and using that hypothesis and moved on, but few things are actually continuously validated as still generating value > their cost.
- pjc50 3y agoAsk whom, though? It's usually really time consuming to determine that nobody is using something, and difficult to get permission. Hence in so many of these hero stories, the critical work is done without permission. This morning on bluesky I saw a story of a very hasty onprem-to-cloud migration that was facilitated, and accelerated, by the rising floodwaters drowning the premises.