What's your goal here? If you want a software development job at a software company, you'll probably need to get an actual CS degree. In that case, the answer is simple: enroll yourself into your school's CS program.

Heh, I actually came here to say exactly the opposite. Our frameworks and abstractions have matured enough these days that almost any development position (certainly at the entry level) is more IT/programming than genuine formal CS. Are some CS fundamentals necessary? Sure; it would be a travesty for any self-proclaimed "developer" to go out in the world without enough knowledge of data structures and algorithms to get by and without some understanding of what lies behind the abstractions. However, none of that requires a full CS curriculum.

Furthermore, the beauty of CS (as I see it) is that it's probably the only technical discipline which lends itself well to autodidacticism. Other hard sciences and engineering disciplines aren't very accessible to cheaply work with hands-on, but with CS literally everything you need is a computer and an Internet connection. If you can do without rigid structure and in-person lessons, enough commitment will earn you the equivalent education of a good university CS programme.

---

My suggestion to OP and others in the same position:

• Stop using Windows cold turkey (if you were on Windows to begin with); OS X is okay, but Linux is better

• Complete the intro Codecademy lesson

• Udacity: CS 101

• Udacity: CS 212

• Udacity: CS 253

In total, this sequence should take six to eight months. Concurrently, take the following math courses:

• MIT OCW: Single-Variable Calculus (includes video lectures)

• MIT OCW: Mathematics for Computer Science (relevant video lectures)

• MIT OCW: Linear Algebra (includes video lectures)

During this process, just to get a good feel for the "real world", you should ideally keep relatively current with software advances and tech news (don't overdo it; reading Hacker News every once in a while is enough); spend the odd weekend doing a Codecademy mini-course or two; and work on occasional small projects (nothing major, because it's too early to lose academic focus given that whatever you build will basically suck; local "hackathon" events are great for experimenting). Experiment with both "standard" software stacks (e.g. PHP Rails or Django with PostgreSQL on EC2) and "hip" software stacks (e.g. Node.js with MongoDB on Heroku or Go on Google App Engine); get to know mainstream frontend libraries (e.g. Twitter Bootstrap, jQuery) as well as more experimental ones (e.g. NowJS, Firebase); learn about desktop and mobile development (Qt, Android, iOS, PhoneGap, Titanium, etc.).

This focused academic sprint should last you a year or so, but by the end of it you'll have a solid foundation.

With that out of the way, you need two things: experience, and a broad high-level cognitive schema for all the major topics in CS.

To address the former, start doing shit. Make it your full-time job. Get some major projects (what some would call "startups") under your wing, and get other people to join you on some of them. If you do this well, you'll start looking more and more like a real engineer (a "hacker", in tech parlance).

Now, after getting some hacker chops with one or two major projects, you should be looking good enough to get a good internship/co-op (these run every season, not just in the summer); I specify internship/co-op, because right now you're more likely to land a really good internship than a really good full-time job, but after a really good internship you're more likely to earn a really good full-time job. Get your resume in order (include all your online coursework, new skills, and especially independent projects), and spam it everywhere (here's a good list to start with; for the larger companies you can apply to ~10 or so different positions at once).

To address the latter, go through this list. Every topic in there, you should over time learn to either discuss intelligently or at least demonstrate a passing familiarity with. Don't waste your time on a dedicated course for anything (unless you have the time and you're really interested in a topic); instead, in your spare time just get some quick unstructured reading down, which can even just be the linked Wikipedia articles (the history sections are nice to know as well).

With all this under your belt, you'll be way ahead of the average CS rising junior who started learning after high school (at least as far as software development/engineering is concerned), and when you add in the next two years of career advancement and self-study, the fresh CS grad Joe Six-Pack will look like a chump next to you.

---

P.S. Mark Zuckerberg was a psych major too :).