Nitpick but nothing grinds my gears more than people using niche acronyms without first defining them in long form, especially when its something like MP3 that's going to give you a million hits of the wrong result when you try and search for a definition.
In all fairness, the intended readership of that blog would know it. It's like handing a random technical Go or Rust post to a strictly-business non-technical person.
Even in my highly technical field we still define acronyms when they first appear in a manuscript, since while everyone works in the field maybe not everyone works in this specific niche and is familiar with all the jargon. Editors or reviewers will want to see it defined in long form. It's really just lazy writing to not do it.
