I think the best practice might be to pare down the navigation to the most important items, so at least those have visibility in a mobile context. However, these are still new design patterns being established, so nobody really has solid answers yet.
You see, Information Architecture has more to do with capital D Design, not fad, bandwagons and styles. Its about solving this exact problem. I really hope the concept of User Experience dies in a fire so we can go back to real Design.
(User Experience is in my opinion the most nebulous, snake-oil concept I've heard since SEO. Users don't want "an experience". They want to get in get what they want and to get out. The experience should be invisible)
There's cross-over, but one "Designer" can't do it all, even if they have a good grasp of everything.
When the focus is on UX, decisions might be made about how people sign in or out. The UX expert might determine that a 2-step log out process is one step too many, but the research they gather might suggest it's nevertheless still acceptable enough to get away with. The designer makes whatever-step process look and function the best it can, without needing to scrutinise the research and testing around 2-step sign out processes.
Another example - consider the user experience of dismissing the banner that appears on some websites that have an app in iOS Safari. The little 'X' close link is tiny, way smaller than any touch button or link should be. Bad UX? Sure is. But the UX person must have data suggesting that having a stupidly small close button for that banner is worth it for the primary visual incentive to act on the promotional prompt without annoying too many people (annoys the hell out of me, but I'm not everyone).
By the way, it's not "an" experience, it's "the" experience, and nobody would agree more with you about it being invisible than the coiner of the term UX - after all, Don Norman's seminal work (The Design of Everyday Things) was all about designing stuff to be more intuitive and fast to use.
SEO might have plenty of snake oil vendors, but it is, unfortunately, a very real and immensely lucrative thing. Search engines drive traffic, which drives money. Search engines are gameable. End of story.
One approach is to build a hierarchy
The hamburger menu only makes sense when it's the literal junk drawer of the app/site, when there's no possible way to categorize its contents with anything more than the completely generic 3 horizontal bars. But primary navigation elements are not junk and don't belong there.
This a a little hyperbolic. If you want surface a link to the Lifestyle section, then you also have to accept that links to about a dozen other sections need to be visible as well - on mobile, this would lead to about a third of the visible page (or more) being consumed by navigation links. Alternatively, you put the nav at the bottom of the page, but I would argue that doing so makes it less accessible/visible than it would be in a hamburger menu.
The real challenge is not when you're trying to put 3-4 links or nav-groups in a hamburger menu, but when your site structure is so flat/shallow that you have a dozen or more equally-viable nav/action options for users. Except for the NBC example in the article, the nav in the examples can be distilled into a narrower, deeper structure.
The article author doesn't appear to realize that on NBC news, the hamburger-equivalent "more" menu still appears at mobile widths. Sometimes it really is a decent solution.
This is a big part of the problem. Devs too lazy to use media querys to adapt the layout to the screen. We end up with poorly implemented "mobile" sites on our big, wide desktop screens. It's like the web took a step back to 1995 with pages hardcoded for 640px width. Looks good on my iPhone... time to deploy.
A hamburger menu that can be optionally converted to a persistent sidebar on screens with sufficient space would alleviate much of the usability problems.
As a trivial example, you could have a single menu labelled "Sections" with a disclosure arrow, and mousing over / tapping it would then reveal a list of all sections. It's functionally identical to the hamburger in actual usage, but because it's called "Sections" (and only contains sections, not arbitrary junk), it becomes an obvious thing for users to interact with if they're looking for the Lifestyle section.
This is a little hyperbolic. You've basically recommended a labeled hamburger menu - 'Sections' instead of 'Menu' - and text labels definitely have a demonstrable advantage over icon-only buttons, but the OP isn't advocating for text labels instead of the hamburger icon (see NBC example that had a labeled hamburger menu originally), it's proposing that the menu items be surfaced into tabs, segmented controls, and lists. That's not viable on sites with a flat structure.
nytimes.com uses the hamburger icon with the 'Sections' label, as you suggest, but it's important to acknowledge that this is just a variation on the theme, not a complete rejection of the 'menu items hidden behind something else' principle, so we need to be precise about the problems that a hamburger menu can and can't solve.
So basically, what I'm saying is that if you must use a menu, label it appropriately, and only put relevant items in that menu. If you have a bunch of things that aren't related to each other, they should be in different menus. A real hamburger menu is only appropriate for items that the vast majority of users are expected to never click on, and for which you're ok with making it hard to find for the rare user that actually does need it.
[1] Well, anything that you want users to actually click on.
Well, if there is such a menu, where else would it be?
In a mobile app it makes a lot more sense, because screen space is so limited and the hamburger button will occupy one of the prime navigation points in the app UI (typically the upper-left or upper-right navigation button slots), so there's obviously not very many possibilities to find something, but even there, if you can possibly avoid using it, you should. As the original article demonstrates, hiding your navigational elements, even on mobile apps, significantly reduces user engagement.
In a desktop website, I can't think of any reason why I would ever use a hamburger menu. Other, more specific menus, sure (e.g. "Sections" in a news site). But if I see the hamburger menu, besides thinking that it's really out of place when not in a mobile app, I also will instantly assume that it's the place to find things that I probably will never need. Basically, if it's something that you might put in the footer of your site, then hiding it in a hamburger is fine. If you think it's something that enough users will want such that the footer would be inappropriate, then don't put it behind a hamburger either.
Then have a menu named "topics" (or whatever marketing says to call areas of news). Still makes more sense than a menu whose icon means nothing more than "this is a menu" (and doesn't reliably convey that to everyone).
I really hate hamburger menus on desktop because as you say, it only says "this is a menu". On mobile: navigation, on desktop (FF & Chrome) it means options. And then on Chrome they have tried to shoe-horn everything into a stupidly small pop-up where half the options are just links to open more options. It's hardly a step up from a menu bar.
Or maybe it's a Markov chain! Move an item in the list by a random proportion weighted by how frequently that item has been used in the past! Infrequently used items have a low probability of making it into the most-recently-used list, where they would supplant more frequently used items.
Or more direct: just always sort items by how frequently they've been use over time, but never allow the top 4 to be rearranged, even if one of the "lower" items gets used more.
Or more simple: just let the user choose which items they want to pin to the front view.
A tab bar is great in an iOS app with a limited scope of functionality. That just doesn't work a sprawling news site covering dozens of topics. A small, product-focused website may even be able to get away with showing all of their navigation options at once. For many sites, however, it's unfortunate, but sometimes you just need a well-organized junk drawer inside a hamburger menu.