The post was a little disjointed, but there were two things I wanted to comment on: 1) Just build stuff. I think this, by itself, is pretty good advice. I've

The post was a little disjointed, but there were two things I wanted to comment on: 1) Just build stuff. I think this, by itself, is pretty good advice. I've built a lot of websites and apps, and while I haven't gained a lot of notoriety or huge financial success from them, they have all been huge educational experiences for me, and are a big part of the reason I have such a good job (and good opportunities) right now. I'll keep building stuff because I find it intrinsically rewarding and educational, and because I figure the more stuff I build, the better the chance that one of them will turn into something bigger. 2) Don't get a CS degree. I cringe when I see stuff like that. This was me a little over a decade ago when I was planning for college. I had the grades and test scores to study CS at Stanford, MIT, or any other well-respected school and for a variety of reasons (that don't make much sense to the 29 year old version of me) chose to study Finance at a few state universities instead. Finance was interesting, and I got to do an internship at a VC fund as a result of it, but ultimately, not studying CS has been a major regret of mine. I feel like I'm a pretty competent and successful software developer now, but I can't help but wonder how many more opportunities would have been available to me had I gone the CS route (or at least Physics, Math, or Engineering) instead. It certainly is worth thinking about whether you really want to go the CS route, but don't write it off because you feel like you can simply learn it all along the way.