11–20 of 33 posts
Finish school. Startups will wait. In the meantime, see me re an internship.
Rather than giving all that money away needlessly, spend a fraction of it on room and board and spend the majority of your time teaching yourself. You'll be done way ahead of 4 yrs.
And then jump into the startup world.
Also, if you haven't already, learn functional programming.
http://news.ycombinator.com/item?id=1327632
Which programming book you just couldn’t stop reading from start to end?:
http://www.reddit.com/r/programming/comments/7s383/from_nand...
I got the same thing from my CS education, but by accident. You can get it packaged neatly in one place from this course. This alone will put you in the top half of the programming community with regards to knowledge and overall understanding.
Finish school. Startups will wait. In the meantime, see me re an internship.
I disagree. If anything, it's school that can wait. Especially considering you can get a decently comprehensive CS education w/o paying mid-5 figures a year in tuition. Rather than giving all that money away needlessly, spend a fraction of it on room and board and spend the majority of your time teaching yourself. You'll be done way ahead of 4 yrs. And then jump into the startup world.
http://www.paultaylor.eu/stable/prot.pdf
and this:
http://folli.loria.fr/cds/1999/library/pdf/curry-howard.pdf
and this:
http://www.cis.upenn.edu/~bcpierce/tapl/
very, very carefully.
Earlier quoted context omitted.
I disagree. If anything, it's school that can wait. Especially considering you can get a decently comprehensive CS education w/o paying mid-5 figures a year in tuition. Rather than giving all that money away needlessly, spend a fraction of it on room and board and spend the majority of your time teaching yourself. You'll be done way ahead of 4 yrs. And then jump into the startup world.
You don't go to college just to study.
I tried to finish school later, but work always won. I never had the discipline to do both.
To keep up:
1. Read CS textbooks and do small projects to make sure you understand the material at a practical level.
2. Join the ACM and keep up with interesting publications from their electronic library. (The Usenix papers are free, but more limited in scope).
3. Learn a new programming language, server technology or OS environment at least every year. Keep your level of exposure to new things high and don't get too comfortable in one thing. Don't be a zealot and don't get stuck.
4. Read a LOT of code. (I read through the Unix sources, the source for TeX and a bunch of other largish packages just because they were there).
More recent things that I didn't have access to: Publically available course videos and material. My guess is that these are as good as the amount of time you put into them.
I'd suggest you look into machine learning. It's probably going to be the single most important area of computing in the years to come. Start with the Stanford course online. Also, if you haven't already, learn functional programming.
Can you attempt to explain it to me?
MIT open courseware might be a good place to start, although I've never used it myself.
http://ocw.mit.edu/courses/electrical-engineering-and-comput...
I would personally focus on topics that are either historically difficult, or pragmatic.
So stuff like compilers, computability and complexity, operating systems, database systems, cryptography, machine learning, web applications, linear programming, networking. Learning the basics of hardware is important too, although it is more electrical engineering and math theory.