Pseudocode definitely has its uses:
Quality & compliance
Your organisation may be subject to stipulations that certain documents MUST be language agnostic.
Not everyone is a hacker
You'll know what I mean if you have contact with customers, management, architects, engineers..
Not every topic is even related to programming
Process management, organisational structures, ..
You don't want a flame war on your hands
People might take offense if your documentation is biased towards certain languages.
(i.e. Java, that's not a programming language, it's script kiddie BS.
If you took offense to that just now, then that proves the point)
Your devs may be smart but your guru's even smarter
You can face a need to explain a tremendously complicated concept to adept coders.
Likewise, however smart you are, there's always someone cleverer than yourself
You're pretty smart. I'm pretty smart. One thing I learned over the years is that there's people out there who are just, simply, WAY smarter. When you meet such people, you'll be glad they used pseudocode to explain their ideas. Check out some of the papers at ACM
Nobody probably likes
pseudocode, but it's good that it's there.
Forcing it on people out of principle, is lame though.
Linux dev and oldskool elite