Getting a CS job but not EECS....

<p>A is sorta a survey of random stuff, different languages and paradigms, etc.</p>

<p>B expects you to have some knowledge of code going in. My class didn’t go much beyond the sort of stuff my highschool CS classes had taught. Topics are data structures, object oriented programming, etc. Some algorithm stuff, a bit of analysis. Probably the most relevant if you’re looking for how to write code that works and the basics of the fancy stuff.</p>

<p>C goes more into the hardware side of things, how the cache works, the internals of a processor, what makes code go fast.</p>

<p>I haven’t taken 170 yet, but that’s generally at the top of the list of things a CS major should take. It might be tricky to get into though, if you’re not CS.</p>