Hacker News new | ask | show | jobs
by foolinaround 1943 days ago
First time I am hearing about Bradfield courses.

What makes them better than the online MOOC courses at Stanford, MIT, etc?

1 comments

I'm biased because I've become great friends with the bradfield founders (Hi Myles and Oz!) since I took all their classes years ago, and recently guest lectured as part of their databases class, but they're basically targeted at working bootcamp graduates that have huge C.S holes in their knowledge. More of a practical focus than what I would imagine you get from online MOOC courses (plus live instruction), but to be honest I haven't taken a lot of MOOC's personally so I may not be the best to compare.
Richie -- absolutely absolutely stunning and incredible!

I thought I was making strides. I've taken two BradfieldCS courses and have had some personal mentoring from Myles even before Bradfield was born.

If the original question asker is reading this thread, I can lend some more insight having done MOOCs and Bradfield.

First off, Oz and Myles are behind teachyourselfcs.com, one exceptional and concise site which their curriculum is sort of based off of. Oz is also the author behind, "You Are Not Google" that was HUGELY popular on here a couple years back.

The thing that Oz and Myles brought was their incredible enthusiasm coupled with their passion for mathematics and computer science. They were practitioners teaching at it from a practitioner's perspective with the goal of providing another practitioner the CS most applicable to their jobs. These courses were in-person in San Francisco for a while (but no longer). Look up either Myles or Oz on Twitter and you'll notice that they're very much still engaged in technical conversations and the computer science and how to teach it today.

The one thing I always always took away from the teachyourselfcs.com site is the section under, "Why learn computer science?"

> There are 2 types of software engineer: those who understand computer science well enough to do challenging, innovative work, and those who just get by because they’re familiar with a few high level tools.

> Both call themselves software engineers, and both tend to earn similar salaries in their early careers. But Type 1 engineers progress toward more fulfilling and well-remunerated work over time, whether that’s valuable commercial work or breakthrough open-source projects, technical leadership or high-quality individual contributions.

I have an inkling that Richie, right here, is EXACTLY what they were talking about when drafting this. This blog post exemplifies this.

I've learned so much from the both of them, but I can honestly say, Richie, if you're reading this, this was a f*ckin' gem! Would love to grab coffee with you some time once the pandemic's over.