Live data from Hacker News

Teach Yourself Computer Science

teachyourselfcs.com

231–240 of 273 posts

Re: Teach Yourself Computer Science

#231
post #126

Can anyone with a CS undergrad from an elite US college (Stanford, Berkeley, MIT, Carnegie Mellon) comment on whether they feel their undergrad covered 100-200 hours worth of these subjects? As someone with an Australian CS degree, I feel like my curriculum covered less than half of this properly.

I'm currently studying CS at UNSW and half of these subjects I've taken relevant courses, and the other half are in my future. Where did you have your experience?

RMIT in Melbourne. UNSW is way better than the former, and from what I’ve gathered is the best program for CS in the country.

Re: Teach Yourself Computer Science

#232

At 200 hours per subject, it would take 2 years to complete if studying part-time (20hr/week) during only the working weeks of the year (92 weeks). If you're uncomfortable working+studying 60-70hrs a week, it would probably take 4 years. Are there blog posts around where people share their experience of undertaking and completely this endeavour?

Heck, I don't know of any blogs with people sharing their experience of an undergrad CS degree.

Good point. I’ve been meaning to write up my experience, because I feel that it was really poor and Australian students need to be more aware of how sub-par our CS education system is.

Re: Teach Yourself Computer Science

#233
post #180

Earlier quoted context omitted.

> the most important skill is just being able to solve real problems, soft skills and breaking problems into parts. As well as the ability to self learn and research. Seeing a very non-technical friend of mine being completely immersed in games like "Factorio" and "Satisfactory" where the entire game is essentially just putting constantly more complex and valuable resources together in automated ways is fascinating t…

>> The sheer look of glee and pride when he gives a tour of all the automation around his base is infectious, and although he doesn't share my amazement at my conclusion, I can't help but think that he's already doing what most engineers I work with do every day, and he doesn't even realize it. One reason why I can't really get into Factorio. It's too much like work. The funny thing is I do code at home, for fun, in…

I understand what you mean. While I'm a Factorio fan I felt this way about the graphical-programming zachlike SpaceChem. Too much like work.

I approached Factorio like MineCraft but with the boring stuff automated.

To have fun in a game like Factorio, just mess around - you don't need to make a perfect factory, or compete with your friend.

Re: Teach Yourself Computer Science

#234
post #180

Earlier quoted context omitted.

> the most important skill is just being able to solve real problems, soft skills and breaking problems into parts. As well as the ability to self learn and research. Seeing a very non-technical friend of mine being completely immersed in games like "Factorio" and "Satisfactory" where the entire game is essentially just putting constantly more complex and valuable resources together in automated ways is fascinating t…

God, yes, all the wasted potential out there hurts my soul.

They're having fun and learning. I think it's OK.

Re: Teach Yourself Computer Science

#236

Earlier quoted context omitted.

God, yes, all the wasted potential out there hurts my soul.

They're having fun and learning. I think it's OK.

In cases where the bulk of their time is wasted on a boring job when they could be learning and having fun all the time on something impactful, no that's not OK.

Re: Teach Yourself Computer Science

#237
Of course an MS - which they recommend against - would likely cover additional topics (computer graphics, AI/machine learning, formal methods) as well as follow-on material to the introductory courses listed on the page.

Re: Teach Yourself Computer Science

#238

One thing I'm always amazed by when casually talking to people about what I do is how they don't think they can do it. Many people think that software engineering and programming are some inscrutable thing. Sometimes I try to tell them that it is nothing special, it doesn't take a mega genius or math expert to do it. That the most important skill is just being able to solve real problems, soft skills and breaking pro…

> being able to solve real problems, soft skills and breaking problems into parts. As well as the ability to self learn and research

You are implying, that most people can do that. I think only about 15% of adults can do what you listed.

Re: Teach Yourself Computer Science

#239

One thing I'm always amazed by when casually talking to people about what I do is how they don't think they can do it. Many people think that software engineering and programming are some inscrutable thing. Sometimes I try to tell them that it is nothing special, it doesn't take a mega genius or math expert to do it. That the most important skill is just being able to solve real problems, soft skills and breaking pro…

> being able to solve real problems, soft skills and breaking problems into parts. As well as the ability to self learn and research You are implying, that most people can do that. I think only about 15% of adults can do what you listed.

And only about 50% of people employed as programmers.

Re: Teach Yourself Computer Science

#240
post #71

Earlier quoted context omitted.

I think that CS vs SWE thing happens with a lot of people, and I got caught there, too. Luckily, I ended up really liking CS and it introduced me to the field, whereas otherwise I would've gone for SWE. There really needs to be a 'teachYourselfSWE' for people who are into that.

How can you tell which one is right for you? So many computer scientist graduates I know ended up pursuing software engineering that I've mistakingly conflated the two.

it's really theory (CS) vs building things (SWE). As you want to build larger projects, or build them better, you rely on CS ideas to do that. So SWE is really engineering assisted by applied CS. I've been studying CS for about two years and am only now learning any real application development. You can study CS without ever touching a computer or building an application (though doing both those things will give you context for why CS topics matter).

It's kinda like if you want to build a rocket to get to space, you can tinker with propellant, metal, and fire, and be a hobbyist that eventually you build a rocket to go to space. Or you can be a physicist and calculate everything on paper. To get to space you really need both those people, but the physicist can learn to build and the engineer can learn theory.

Post reply on HN