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.
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.