It’s not explaining any deep technical details. Think of it as a gentle introduction to the idea for someone to explain why they might want to read the paper, before reading the paper.
If the article was intended to be an intro to "Raft" algorithm I would've agreed with your sentiment. But this is what the article starts with:
Understanding Raft can be tough. In fact, I’ve seen conversations recently on social media in which actual technical leaders of infrastructure companies demonstrate a lack of understanding (!). Point being, you’re not alone.
Anyway I now notice that the article was written in 2023, probably I'm being too pedantic.
I think the point being made (I’m not the author after all) is not that they are misunderstanding how Raft achieves consensus, but what it means in the first place when we speak of it doing so and why that’s useful. By “technical leaders” here, one might think of CTOs, directors, and senior managers over technical teams rather than senior ICs.
