OK, well it's great you found something you like, and I don't doubt that there are people who can program who don't like it. I would still claim that just like

OK, well it's great you found something you like, and I don't doubt that there are people who can program who don't like it. I would still claim that just like guitar, it may get more fun with practice, and that practice may take years. Even if you're working on some old legacy system, being the person who can make it sing is pretty fun IMO. Actually I find the legacy stuff to be more interesting because it actually runs and does things in the world. BTW I also found that those kind of debugging sessions went down drastically in frequency in a ~14 year career of programming. (We had multi-week, multi-engineer bugs at my first job in games.) The industry changed its practices significantly, and I also changed my personal practices. It only takes a few experiences like that to reflect on what could have gone differently. Sometimes they are out of your control, but often not. --- edit: If this helps make the point more succinctly, I will also say I was mathematically oriented, and had a masters and BS in engineering from a good university. And I worked on a small team shipping major console games ... and despite that, I got drastically better at debugging and testing in the next 10+ years. (Debugging being the most literally scientific part of programming; I was better at math than science.) Actually the experience of working with game programmers taught me how bad I was at debugging. There's also a lot to learn about software architecture for reducing bugs. If you get infuriated frequently by debugging, then there are things you can do to change that. Of course you may not want to if you've found other things you like.