I agree with the author in that balancing actual work vs. meta-work like writing tickets/documentation/scoping tickets is always going to be a pain point regardless of the project management system in play. Jira can be fine in that regard, but it also gives PMs & managers an opportunity to tinker with things and "improve" workflows in the glorious name of adding value.
It reminds me of the old quote about democracy: "Jira is the worst form of project management software except for all the others".
This is what I believe too. With interest rates rising, companies have been under a great deal of pressure to show profitability, and especially with Reddit aiming for an IPO, it seemed (superficially at least) a great idea to badger their userbase into adopting their mobile app, where they could be monetized to a much larger extent.
So of course they made the conditions of using their new API incredibly onerous.
The whole point was to discourage developers from using it. And then by cherrypicking a handful of select 3rd-party developers to offer more amenable terms to on the downlow, they can show that they were just being reasonable good guys, and doing their best to work with everyone, and that it must be the developers at fault if they decided to walk away and abandon their users.
So yeah, they've managed to get their app center stage, and the only minor tradeoffs have been: