"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
(I know these things are indeed annoying—but that's why we have this rule.)
navigate the UI disaster to read about the UI disaster...
I don't consider this story a UI disaster. Generating different 4-digit codes across terminals for the same object, and recycling those codes regularly... that's a data handling disaster.
That kinda seems feature-rather-than-bug honestly - I read the entire thing because I'm fascinated by UI/UX stories like this, and clicking to open each tab is nbd, but if it had been a topic I wasn't that interested in, I wouldn't've read it. Which means I'm less likely to fall into an attention-grabbing rabbit hole on social media.
As a counterpoint; I really like threaded posts like these. Each post in the thread becomes a kind of sub-heading or meta-paragraph which allows the user to disengage at well defined stops.
At the same time, it’s understandable that people don’t like it. The format has its problems, but I find I will read less of a blog post than a thread all else being equal.
But it does not allow the reader to quickly skim the article. It requires the user to interact with each paragraph in order to enable the user to skim it for interesting words.
Old fashioned non-interactive subheadings would allow the user to "disengage at well defined steps" and also to quickly scan ahead.
I admit I am so turned off by the format I only made it hlf way throught the thread.