I am (was - new job now) guilty of disabling selinux on the fleet of servers managed by puppet. I was hoping that the modules listed in the article would show that configuring selinux is actually easy, but I came away with my opinions unchanged. selinux requires a fair amount of investment to deeply learn how it works and what the requirements are for a bunch of apps. As a developer casually working with the ops team to automate their configuration, I didn't have the time or inclination to undertake that learning for what I perceived to be only marginal improvements to our systems.

For what it's worth, that system had about 60 different applications we were running that were provided by a vendor, and their official recommendation was to disable selinux. They never provided (afaik) configurations or guidance to run their apps under selinux.