I'm not saying make it all work without JS. Provide a noscript tag and actually handle your error states. These are basic best practices. If you get fired for not swallowing errors, I don't know what to tell you.
But that's not what the article is complaining about - they're complaining that most of the UI functionality doesn't work without JS. To make it do so would require a progressive enhancement approach, which is not going to sell well if the only benefit is an extra 0.1% audience reach.
Then perhaps we're not at odds because full JS-disable support is often unreasonable. My gripe was that many of my own experiences using uMatrix with scripts disabled by default ('cause you never know what sort of modals and pop-ups and other junk random pages send you) and not getting even the slightest feedback on what went wrong. I'm aware that this is a minority setup, but throw a user a bone. I've been banned from signups because I failed a third-party CAPTCHA I never saw. I enable JS manually on almost every site once I get an error and it's vaguely trustworthy.