Instead of disabling it, consider putting it into permissive mode. It logs violations but doesn't enforce any rules. It's a good way to get a feel for what it's doing. You can tweak the rules, view the logs, tweak some more, and work up to a tight policy before enabling.
Also, if you disable it, re-enabling requires that you relabel all of your files and reboot the system; the relabel process can take an impressive amount of time.
Switching between eforcing and permissive can be done on the fly with the setenforce command, no reboot required.
I do think that laziness is a virtue in a sysadmin when properly applied, but using selinux is in your best interest.
Also, if you disable it, re-enabling requires that you relabel all of your files and reboot the system; the relabel process can take an impressive amount of time.
Switching between eforcing and permissive can be done on the fly with the setenforce command, no reboot required.
I do think that laziness is a virtue in a sysadmin when properly applied, but using selinux is in your best interest.