I hate when a long technical document doesn't use BLUF, ie omits a summary at the start with the main topics.

There's too much info on the internet, and even in internal documentation: if I have to read half the thing to understand if it's relevant, I'm gonna spend most of my time on irrelevant stuff.

This is a problem with asking engineers to document without having a writing culture. I've seen it happen: once it's written down, that's it: it's documented, great work! But we should treat it more like code, with clear divisions of concern s, scopes and even refactors when needed!