"Declarative programming clears the mind." - Sterling & Shapiro, _The Art of Prolog_
Provided you don't abuse the cut operator, a Prolog program will consist of a series of rules which each have a logical meaning in isolation. Reasoning about Prolog code is so different from trying to unravel what's actually happening with several layers of OO polymorphic dispatch, it's not even funny.
"Elegance is not optional." - Richard O'Keefe, _The Craft of Prolog_
Added benefit: When it is time to start coding, you can amaze your coworkers by brain dumping a decently coded solution at typing speed.
Sitting there with a notepad and a pencil thinking about the problem is when I find I actually solve the difficult problems not when I type furiously at a keyboard.
One day myself and another guy were debugging a piece of code by staring at it, figuring the logic out in our heads and pitching theories back and forward. The boss walked past, saw we were sitting there "doing nothing" and told us to do some work... ugh!
I think that this is valid for most projects in any language.