Beej's Guide to Learning Computer Science
11–20 of 150 posts
Re: Beej's Guide to Learning Computer Science
#12I’ve had Beej’s Guide to C and Beej’s Guide to networking bookmarked for an embarrassing amount of time. But this is the first guide that I know the material! I have “learned computer science” (somewhat). And I have to say it has propelled Beej’s other guides to the top of my reading list. The subchapters I skimmed and their content are just so relevant and I know many new and experienced devs (myself included) who w…
I recently read his networking guide as part of a class and it was invaluable. It gets you up to speed without overwhelming you with detail. It's a lightweight read.
Re: Beej's Guide to Learning Computer Science
#13Most reputable CS courses will have one or two math subjects (often called "Discrete Mathematics" or some variation). Does anyone have any advice on tackling subjects like these for someone who hasn't done any math since high school more than a decade ago (and has forgotten it)?
Re: Beej's Guide to Learning Computer Science
#14Most reputable CS courses will have one or two math subjects (often called "Discrete Mathematics" or some variation). Does anyone have any advice on tackling subjects like these for someone who hasn't done any math since high school more than a decade ago (and has forgotten it)?
Re: Beej's Guide to Learning Computer Science
#15Anyway, the audience is
> Undergrad students just getting into programming
so it's naturally biased toward the engineering part of the subject.
Re: Beej's Guide to Learning Computer Science
#16Well done but is this a guide to Computer Science or to Software Engineering? In a Guide to CS I expected to find information theory, computability, complexity, finite state automa, language grammars etc. Anyway, the audience is > Undergrad students just getting into programming so it's naturally biased toward the engineering part of the subject.
Re: Beej's Guide to Learning Computer Science
#17Well done but is this a guide to Computer Science or to Software Engineering? In a Guide to CS I expected to find information theory, computability, complexity, finite state automa, language grammars etc. Anyway, the audience is > Undergrad students just getting into programming so it's naturally biased toward the engineering part of the subject.
Reading the chapter of AI seems to support that feeling. It was about tips on where to use it, where to not use it as a shortcut, how to be critical of any output, and some personal speculation.
Re: Beej's Guide to Learning Computer Science
#18Well done but is this a guide to Computer Science or to Software Engineering? In a Guide to CS I expected to find information theory, computability, complexity, finite state automa, language grammars etc. Anyway, the audience is > Undergrad students just getting into programming so it's naturally biased toward the engineering part of the subject.
What about operating systems, architecture, compilers, networking, and the like? I have seen people argue that computer science is the more theoretical side of things, but many university CS programs cover both systems and theory (or sometimes skew to one side).
Re: Beej's Guide to Learning Computer Science
#19> You gotta want it. Do you want it enough to go through the tremendous amount of effort it takes to learn it? Maybe you hate programming, but you want the money enough. Maybe you don’t care about the money, but you want to program every second of the day.
> Just make sure you have the drive to make it happen.
Man this is so true
Re: Beej's Guide to Learning Computer Science
#20All of his material is absolutely top notch. His guide to network programming was instrumental to both my understanding and career. It often feels like thanks isn't quite enough.