Trying to develop a salary + cost of living model that doesn't take into account one's personal priorities and preferences is foolhardy. And the piece Hired wrote did exactly that.
News flash: not everyone who lives in NYC or SF is paying $3000 a month in rent. Many of my friends in NYC are paying $800-1200 for a room in Brooklyn with a 25-35 minute commute on the subway. My friends in SF tell me that they pay more but certainly in the 1000-2000 range not the 2000-3000 range that's always quoted.
Get a significant other and move in together and you can split that in half.
But yes, if you want to live alone, 5 minutes walk from Mission Dolores park in SF or bring a family into Palo Alto then the bay is the worst paying place for you as a software engineer.
On the other hand, if you're willing to commute, or willing to have roommates, cook at home instead buying into the myth that you _have_ to go get brunch at some $12 avocado toast cafe, then you'll likely save more money in the long run in SF or NYC than in the Midwest, and yes, after cost of living and after tax. Unless during your job search you find yourself in the enviable position of finding salary offers in the midwest that are very close to the same salary offers you get in the high COL cities. If you do find that though then by all means live in the midwest. And those situations do exist but it's just that there are far fewer $100,000 jobs in Des Moines, IA than in Brooklyn, NY.