Introduction
Welcome to Bite-Sized Mathematics for Computer Science!
Let's start with some important points:
-
This is a learn in public project, rather, an experiment. That is, there is some chance that there might be mistakes. For feedback, feel free to contact
edae dot space at gmail dot com
. -
The best way to learn something is to talk/write about it, or teach it to someone. This is the crux of the project: this collection consists mostly of very short notes written in an informal tone to get familiar with the concepts.
-
The structure of this work follows from the course material: there are 4 units, each with a varying number of sections. Those sections are intended to be as short as possible, or bite-sized.
-
That said, it is not a full go-through of the course material (that would be very daring!). In fact, it is mostly that I used its syllabus and the general overview; that's why the title Notes on MIT's 6.042J might be misleading.
-
The main goal is to get familiar with the concepts rather than do a deep-dive exploration. That's why so many things are left off.
-
If you encounter a sentence like "let's prove it," don't expect a rigorous mathematical proof. It is just a very, very informal way to convey the idea, the reasoning, of a proof that's given in the course or the coursebook.
-
Some of the examples are from the practice exercises in the course's relevant section; some of them are from other resources. Sometimes I provide a solution I came up with myself; sometimes it's from the lecture videos or the coursebook.
-
This collection as a whole will probably make the most sense as a very short and informal supplement to the course, especially if you don't have a mathematical background but still want to browse the material.
-
Still, there are some prerequisites. It is assumed you have studied a bit of math before. The course itself requires background on Single Variable Calculus, and familiarity with sequences and series, limits, and differentiation and integration of functions of one variable. I provided some resources that I found helpful in the Prerequisites & Resources section, but here is the thing: a lack of background knowledge shouldn't deter you; quite the opposite, that means there's still a lot more opportunity to learn. That's a good thing. I don't think you need to be an expert on these subjects either; since this collection is only to provide familiarity with the concepts, that's okay if you don't know the intricacies of a topic.
-
Sometimes, a section only consists of definitions without examples. These are just notes. The point is to keep it as simple and short as possible. Here and there, when there is no example, I provide links to other resources that explain the material at a very basic, introductory level.
What is 6.042J?
6.042J, Mathematics for Computer Science, is a free course that's offered through MIT's OpenCourseWare. There are several versions of the course, this work is based on the 2015 one.
Why write about mathematics when you don't have a formal education in it?
Because I want to.
Learning is, admittedly, slow — especially mathematics. But I want to document what I'm learning as I'm doing it; that's the point of learning in public.
Couldn't you have chosen a simpler resource rather than picking up an MIT course syllabus to "gain familiarity with concepts"?
Yes, I could've. There are tons of resources, as I included in the Prerequisites and Resources page. However, it's easy to get lost in details; 6.042 is structured, and it is a challenge. And it's fun.
I also enjoyed Albert Meyer's explanations and teaching. That's another reason.
You don't go through the problem sets, or the exams.
That's correct, and it's intentional.
Again, the point is to be as short as possible, only to explore concepts, so it mostly just scratches the surface.
So, it's normal that ${subject}
is left out in ${section}
. There are many things left out.
Some points on notation:
- The coursebook and slides use the symbol
(as in , is defined to be ). I used (the equal sign) for this. - "iff" is the biconditional, a shorthand for "if and only if", you can check out Logic and Propositions, so it is not a grammatical mistake if you've not seen it before.
"Anybody with enough curiosity ought to be able to explore a field.*" - Eric Grimson, Chancellor for Academic Advancement at MIT, Professor of Computer Science
*From MIT's Chalk Radio.