The person listening learns something new, and is able to see something beautiful in the way that someone else sees it. Additionally, the person who's doing the explaining gains the experience of trying to relate their idea to another person, an exercise that often expands the explainers understanding of the idea.
I really wish more people explained what they love and find interesting!
But it's a very different kind of explanation than "here are all the building blocks you need to put together in order to understand how wrong the way you're currently doing things is." The second kind is pretty much what all "innocent programming questions" require in response.
I exhort everyone to strike up these kinds of conversions especially with strangers as often as possible - I guarantee you will learn something interesting :) Ever since I got the hang of it, it has really enriched my life.
Done properly, it's fun, though you do need some form of ongoing trust - it's not something you should do to someone piping up for the first time on IRC.
Feeding pigs is the tip of the iceberg. If you want to see some sparks fly, just sit down at the local cafe and talk about the comparative yield of soybeans and corn, and why anyone growing X percentage this year with the weather pattern is just plain nuts.
It's not quite the same as the family-farm days (most are now corporate owned), but those were the first debug sessions I listened in on as my grandfather held court among his colleagues.
For programmers, everyone is trying constantly to braindump to everyone else; that's half of what the blog posts on HN consist of. And everyone wants their braindumps analyzed, and, more importantly, debugged. "I'm feeding my pigs horse meat--did I make the right decision?"
When you're exposed to it so often, it's hard not to get tired of telling people about the benefits of grain over horse meat.