There are a couple things this article glosses over. With Vercel vs. Netlify, be mindful of the many other fees they charge besides bandwidth. I wouldn’t be surprised if the costs are comparable when that’s accounted for. Sometimes the answer with these things is just to be diligent. Don’t be surprised at what you get if you stick your hand in a meat grinder. Put up guards in your CI process if you have to.
The other thing is that I’m not sure how willing I am to jump to endorse an efficient cache policy as a blanket prescription like they seem to. I suppose I’m not opposed to the advice, but it has very strong “draw the owl” vibes. Project requirements vary, and I’d even argue that sometimes minimal or no caching is wise when requirements are subject to change or you’re doing a lot of static deployments because the savings can sometimes not be worth the headache. End-users are very demanding nowadays. Sometimes “it’ll roll over soon” isn’t good enough. Caching is tricky. Make sure you really get it right in addition to doing the math on the cost-savings if you go down that road.