AppArmor has come a long way. It's worth learning about it. They have quite a few builtin profiles that you can take advantage of.
Like, the tone of the comment makes no sense, the hard part isn't on the OP, and OP wasn't saying AppArmor is easy, just the content of their comment is easy (which it is!)
It's like saying flipping a light switch to turn on a light is easy... the having someone fly in complaining that understanding industrial power generation is not easy at all.
It's not, it has subtle gaps in the sandbox which still allow some of the attacks it's supposedly protecting you from.
My point is: how do we know the instructions are actually safe?
If you don't trust it, don't run it... but I don't know how anyone in software development would be unable to function if they've never been able to trust someone else's config file suggestion.
None of this applies to maintaining my development machine. You might want to revisit your gate keeping.
And the little demo script GP wrote seems pretty straight forward to me.
If this policy isn't available and enabled by default in some package containing common policies, do you really expect your average developer to a) even know anything about AppArmor, or b) know how to write an AppArmor policy file without spending a few hours digging through docs, reading examples, and engaging in a bunch of trial and error?
(If your answer is "yes" to either of those questions, I'd suggest you might overestimate what is common knowledge.)