First ... So don't take a stereotypical coding job; whatever your definition of that may be. I've personally in general avoided big companies my whole career to avoid what I see as the stereotypical coding job - too many meetings, too much waterfall style development and way too much bureaucracy which I find myself unable to navigate. It's served me fairly well in that I get a chance to do a lot of different things. Small companies need more versatile staff - people who can do systems and network work as well as coding. Who can help design and architect systems as well as coding. These things from my standpoint let me enjoy technology while not going insane spending 12 hours a day producing cogs and widgets. And of course the option exists for you to go the route you are obviously culturing of Entrepeneurism. If you can handle both the technical and business sides you may have an advantage as you can work both sides of the equation. But beware of becoming the dreaded business-guy who produces crappy code and expects his programmers to take it as holy writ from upon high. If you plan on blending business and technical keep your skills and knowledge polished and relevant. (Yes, I've had a few of those. Including one who would "Align" all his code in the gutter [aka no freaking tabs] and freak out if anyone reformatted it)
Second... The degree does not make the man. Personally, I'm an autodidact although I originally pursued a Criminal Justice degree. The best programmers I've worked with personally (keep in mind the plural of anecdote isn't data) have all had either no degree, or had a degree in an unrelated subject. I've worked with chemistry, physics, English and history majors all of whom were stellar programmers. While the fundamentals are important, it's the capacity for learning and doing something that you enjoy that matters much, much more. If you think you have the core concepts of CS at a point that they're useful to you, change majors. Go get a business degree, or one in physical education if it makes you happy.
Just use what you know, and what you think you can learn in the future to best advantage.
Comments
A few thoughts come to mind here for me.
First ... So don't take a stereotypical coding job; whatever your definition of that may be. I've personally in general avoided big companies my whole career to avoid what I see as the stereotypical coding job - too many meetings, too much waterfall style development and way too much bureaucracy which I find myself unable to navigate. It's served me fairly well in that I get a chance to do a lot of different things. Small companies need more versatile staff - people who can do systems and network work as well as coding. Who can help design and architect systems as well as coding. These things from my standpoint let me enjoy technology while not going insane spending 12 hours a day producing cogs and widgets. And of course the option exists for you to go the route you are obviously culturing of Entrepeneurism. If you can handle both the technical and business sides you may have an advantage as you can work both sides of the equation. But beware of becoming the dreaded business-guy who produces crappy code and expects his programmers to take it as holy writ from upon high. If you plan on blending business and technical keep your skills and knowledge polished and relevant. (Yes, I've had a few of those. Including one who would "Align" all his code in the gutter [aka no freaking tabs] and freak out if anyone reformatted it)
Second... The degree does not make the man. Personally, I'm an autodidact although I originally pursued a Criminal Justice degree. The best programmers I've worked with personally (keep in mind the plural of anecdote isn't data) have all had either no degree, or had a degree in an unrelated subject. I've worked with chemistry, physics, English and history majors all of whom were stellar programmers. While the fundamentals are important, it's the capacity for learning and doing something that you enjoy that matters much, much more. If you think you have the core concepts of CS at a point that they're useful to you, change majors. Go get a business degree, or one in physical education if it makes you happy.
Just use what you know, and what you think you can learn in the future to best advantage.