It depends on your audience.
If you have a young (in-spirit :-), vibrant development team who are avid internet users and follow trends, terminology like epic FAIL (anything that went spectacularly, or publicly, wrong), Pokemon exception handling, 'All your base are belong to us' (deployment/security FAIL), ninja-coding ( bleeding-edge code) etc, are fun to use and help the working day along through humour.
Some team members just might not read all the same resources and there's a risk they'll feel left out/not with the in-crowd. In that case, someone needs to translate or highlight what matters and what's just office banter.
A lot of words and phrases fall out of fashion after a while, so one has to keep up in order to understand and be understood. This can be an effort in itself.
If you're in a senior position or one with project management or budget responsibilities, you'd need to get a feel for the language of the business before saying "there's too many chickens and not enough pigs in this project - no wonder the code smells", which might confuse as pigs are smellier than chickens IRL.