The problem is that if you don't know what good looks like, you don't know that your thing isn't good and you may not even know how to recognize someone who can review it for you.
The question to strive for: "if someone doesn't know me or my work and my company at all, can they look at my resume and understand what I've done, why it's impressive: and why I am an interesting candidate?"
As someone who sits on the other side of the table all the time, when someone has structured their LI/resume this way, it tells you they (1) cared to do it well (2) found a way to understand what's relevant and (3) found a way to implement it: those add up to a very strong signal layered on top of their technical skills.
Someone will inevitably reply that you can be a great dev and a terrible writer and I guess that's true but it makes it so much harder for someone to "see through it" and hire you.