A month in south East Asia.
Then another month simply learning something new. Get excited about programming again. Make programming your hobby again, and not just your job.
The first time I experienced burnout, I didn't fully understand what was happening, so I kept spending 12-16 hours a day staring at my desk. My productivity got close to zero for what I think was well over a month. In retrospect I think I should have:
a.) accepted that I've begun to experience burnout
b.) recognized that I would lose some output over this
c.) talked to my boss and organized a week or two of out-of-office time to reset.
Not really burnout but a lack of enthusiasm for the job a few years ago. Until I got a new job building something from scratch, learning Django. M
aking use of my existing database skills. I think too many new things at once can get a bit overwhelming but coming from Perl, Django and Python were easy to pick up. It was a nice balance of using my existing Perl / Database skills as well as learning new stuff that felt productive.
Obviously it would be impossible to continue doing what one was doing. So, one should just stop, do something else, learn something new and it'll pass in a year.