No. I always had a purpose to program more than the client needing it. I have always worked on products, and was always allowed to explore my creativity, so that might also be a reason. Programming was always "goal oriented" for me - either having to simulate an engine for my BE project, or creating components for our products to differentiate from our competitors, thus maximizing hikes which allowed me to pursue other interests, or lately, starting my own company. So, while I have experienced several minor burnouts, which lasted many weeks to a few months, I have never had any regrets. I hope to gracefully transition to pursuing other interests in a few years, and I will fondly remember this programming phase.

Based on that experience, my guess is that those who regret are usually those who just go through the motions. They most likely don't have side projects, or ideas to pursue, and the monotone of programming gets to them. Lets face it, our industry is all about repackaging the same old solutions, but for different clients, and that's quite boring. I like to imagine that engineers in other fields do a lot more than what programmers do, which makes things different even when repackaging solutions, but I could be wrong. In Indian context, there are many people I know, ranging from senior engineer or VP, working in multi national companies, with very good salaries, but are quite disenchanted with their jobs because they are nothing more than glorified bricklayers working in India while the architects send out instructions sitting in USA or Europe.