I have to disagree. When I’m reading API documentation (or a particular bugbear, a recipe) then yes, cut the crap and get to the point. But when it’s an article

I have to disagree. When I’m reading API documentation (or a particular bugbear, a recipe) then yes, cut the crap and get to the point. But when it’s an article like this telling the story of the rise and fall of a business? I want to be taken on a journey, not receive a bullet point list of things they did wrong. There’s no reason why this topic should not be covered long form style.