Anyway, the audience is
> Undergrad students just getting into programming
so it's naturally biased toward the engineering part of the subject.
Anyway, the audience is
> Undergrad students just getting into programming
so it's naturally biased toward the engineering part of the subject.
Math, physics, statistics
Theoretical CS, the one in my original comment
OS, compilers, networking, computer vision, transmission codes
Computer languages and having to write actual programs, how transistors work up to logical gates, adders, CPUs and machine language
Of course the separations are not clear cut: we had relational algebra and SQL commands in the same course.
> Are you getting into Computer Science, or thinking about it? Or maybe you’re in it already. This super-high-level guide is for you!
> I’m not going to talk about how to write code (much). I’ll I’m going to talk about in these roughly 40 pages is more about how to learn when you’re a nascent software developer.
Page 1
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.