Depends. What problem are you trying to solve? If your problem is mere employability, you've already solved that. Actual work experience with Rails and a modern

Depends. What problem are you trying to solve? If your problem is mere employability, you've already solved that. Actual work experience with Rails and a modern stack (with the added plus of a four year degree, albeit non-CS) is enough for a massively buzzword-compliant resume. And with a business degree and that kind of education, you might be better off focusing on the business problem space rather than the programming space. Keep programming, but be a real-problem expert. Frankly, people who speak both programming and business adequately are more valuable than specialists who know one but not the other, in many/most cases. So you already have enough to choose your job. Missing a CS theory question in an interview should not be the difference between pay-rent and no-pay-rent for you. Therefore, the reason to learn deeper CS theory is because you WANT to learn it, because you find it interesting for its own sake, because you want to master your craft. That's good, that's pride. In that case, study some well-regarded algorithm/data structure books and other classics, do code katas (google it), maybe even go back to school and get an MIS degree. I'd also recommend learning languages. C in particular is important, because it will teach you how memory is managed. If you've never had to manage it manually, there are a lot of things you don't understand. This doesn't mean I recommend manual memory management (geez, if ANYTHING invites automation, it's memory management!), but it's good to understand how and why.