To each their own. I know plenty of people in various online communities who choose to program as a hobby, and would not dare do it as a profession. It goes with many of the "production skills", or you could even call them "artistic skills". Many, many people love to draw and create visual art. However, a large portion also prefer to not get a graphic arts degree and pursue paid employment doing it. Why? They want to do what they want to do, when they want to do it, how they want to do it. There is nothing wrong with that at all.

I will say, though, that if you have a love for computers and economics, you could major in CS and minor in Economics (or vice versa; I am not sure which would be more optimal). You would be much loved and in high demand, as Economics applications are being built every day, and you could have much more valuable input into the project, instead of being a programmer that needs all the design handed to you. You could also float in either direction, working up straight programming resume stuffers, and straight economics work stuffers as well.

However, I don't want to sound like one of those people who tries to get you into the same line of work that I enjoy. If commercial coding work is not for you, its not for you. Pursue what you love.

Well that's good you figured it out sooner than later to save yourself time and money if you are paying for college anyways.
But do keep in mind that programmer is consistently rated as one of the top jobs you can get up there with college professor so there are worse fields you can go into for a career anyways.
Unless you are self-employed or independently wealthy you will almost always have deadlines and someone telling you what to do so going into another field isn't going to change that. Sound like you need to get some more intern jobs to be completely sure of yourself or you wouldn't be posting this.
That's why some companies like Google give their programmers perks like 1 day out of 5 where they can work on their own programs to keep them happy. But in the end all that matters to the employer is that you are able to ship in the end even if you consider the code ugly or not optimal.
The bottom line is that a lot of the time it's OK to create a solution that solves 80% of the problem. Always remember that shipping is a feature.
That's the other thing to keep in mind is that just because your first job programming sucked doesn't mean they all do.
On the otherhand if your aren't one of those 1 in 100 programmers that can code around everyone else then it's probably better for your health since you will always get stressed about not being able to keep up with your coworkers or meet deadlines and being stuck in front of a computer 8x5 in a cubicle ain't going to help much.
While I think I'm decent at programming I also don't really care to be in a cubicle all day in front of a computer and like to get up and wander around and talk to people like you would be able to if you working as the sysadmin or security,etc. So while I like learning about programming, algorithms and all the math behind it, etc. I also cannot image myself in that position for 5, 10 or who knows how many years over and over. Then again I know other people that could spend all day just writing out SQL queries (not my idea of fun) and do it day after day like it's as much fun as going to the movies, going the beach, working on your own unfinished games,etc LOL. I really don't see how they do it? It's like their minds are wired different?
I'm alot more visual person. If I don't see my programming efforts pushing out sprites or images or something cool on the screen I don't feel like it's worth the effort:( The only time I care about the logic or algorithms behind it all is it's a necesary hurdle I have to pass on my end result of making a game or whatever other cool application tickles my fancy.
The only time I mess with SQL is to use it as a backend for my image viewing application to be able to load 500,000+ images without peformance issues, beyond that I could care less if it's not a Turning complete language or what.

Getting back on topic you know if you go into security or network engineering you will still have to do some programming?
he software engineer will specialize in implementing a network protocol by designing the software, testing it, debugging it and assuring that it performs as close to its theoretical efficiency as possible.
The only reason you should even be working a computer science degree instead of just going into IT, which it sounds like you want now, is that Computer scientists show us what can be done by doing it and proving it.
So you should have an advantage over your IT coworkers since you won't waste time trying to solve known unsolvable problems.

Best wishes to all of you. As I explained to a friend, I find programming much like being able to draw a puzzle which is as big as you want, with the shapes and colors you want... it's the ultimate time-slacking solution!

It seems like I've found a job in the field of building integrated photovoltaic but I have lot of expenses and I'm not quite sure I can keep it for long, at the end of the month it never lives up to the expectations.