Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- by vismit2000
- Difficult to give exact recommendations, but explore the materials left from the MOOC era, roughly 2012-2017, when high quality online education was provided for free. For example:
- https://ocw.mit.edu/courses/6-0001-introduction-to-computer-... (https://learn.mit.edu/courses/course-v1:MITxT+6.00.1x) and https://ocw.mit.edu/courses/6-0002-introduction-to-computati... (https://learn.mit.edu/courses/course-v1:MITxT+6.00.2x) which are introductions to thinking in terms of algorithms and to numerical analysis in Python. The code assignments with tests are still available, but I don't know whether they run standalone, and how much work they'll need to update them to newer Python
- https://www.edx.org/learn/coding/university-of-british-colum... and https://www.edx.org/learn/coding/university-of-british-colum... which is an introduction to functional programming where you build space invaders game (or at least that was the game you built in early runs of these courses) in Racket (Lisp/Scheme like language)
- https://computationstructures.org/ this course builds a CPU from the basic gates, and introduces many of the computer science topics. The site even has the lab simulations available, but I don't know whether they are still working
- https://learn.mit.edu/courses/course-v1:MITxT+18.01.1x https://learn.mit.edu/courses/course-v1:MITxT+18.01.2x mathematical analysis
by marcindulak - > when high quality online education was provided for free
Is it not still happening?
- One thing I would add to the excellent suggestions above is that it can be surprisingly useful to go one level below what is usually considered “software engineering fundamentals.” I teach mathematics students, and over the years I've become increasingly convinced that understanding some of the machine underneath makes many higher-level concepts much easier to understand later: memory and addresses, a simple CPU, assembly, calling conventions, and eventually how a compiler translates a programming language into something the machine can execute. There is a pedagogical principle I like: don't learn the solution before you know the problem. For example, pointers become much less mysterious once memory and addresses are concrete. Many programming-language features also make more sense once you have encountered the problems they are designed to solve. This is one reason I like the Computation Structures recommendation above. I've been experimenting with a similar bottom-up approach in an undergraduate course at Ulm University. We eventually go as far as writing a small compiler, and then rewriting a smaller version of it in its own language so that it becomes self-hosting. I've started putting the material in English here:by michael-lehn
- For CS, as in "fundamentals that are behind what a typical programmer deals with every day" there is a good resource: https://teachyourselfcs.com/.by frankie_t