"Common inquiries about the challenge, rules, and self-study process"
The MIT Challenge is a self-directed experiment where I attempt to learn the entire undergraduate Computer Science curriculum of the Massachusetts Institute of Technology (MIT). The plan covers key courses, including mathematics, physics, general science foundations, electrical engineering, software systems, algorithms, computing theory, and electives. The goal is to complete all of it within a 12-month window by studying full-time.
No. I have no official affiliation with the university. I am not enrolled as a student, I do not attend campus, and I do not receive any credentials, certificates, or degree credit upon completion. All curriculum guidelines and resources are gathered from public archives, mainly MIT OpenCourseWare (OCW), which MIT offers freely to the public. This is a personal intellectual pursuit.
When it is time for an exam (midterm or final), I download the exam PDF and print it out. I clear all reference books, phones, and computers from my workspace. I set a countdown timer for the official class time limit (usually 3 hours). I sit and write the exam on paper.
Once the timer rings, I immediately put down the pen. I then grade my exam strictly against the official solution key provided on OCW.
To pass a course, I must score at least 50% on the final examination. This corresponds roughly to a C- passing grade. If my score falls below this threshold, I consider the course a fail. I must restudy the material, identify my knowledge gaps, and write a different final exam from another semester's course archive to clear it.
Traditional college environments have high structural overhead: commuting, waiting in lines, attending administrative events, writing essays for filler classes, and semester scheduling bottlenecks.
By working completely online, I can cut out this waste. I study full-time (roughly 8 to 10 hours a day, 5-6 days a week), watch lecture videos at 1.5x speed, focus intensely on doing practical problem sets instead of reading textbooks cover-to-cover, and schedule exams immediately when I am prepared, without waiting for the end of a semester.
Yes. Computer Science is an applied engineering science. Watching lecture videos is only 20% of the learning; the other 80% happens when you are forced to debug a segmentation fault, structure a database, or optimize an algorithm's execution. I complete all programming labs and assignments, and the source code is pushed to my public GitHub repository as proof of work.
Yes. While technologies and language syntaxes shift constantly, the mathematical and engineering core of computer science does not change. Modern systems are still built on the fundamentals of compiler design, operating system architecture, computational complexity theory, and discrete mathematics. Learning these foundations is what separates a software engineer from a syntax-coder.