The average University CS curriculum is also broken for most people.
They generally start at a level of abstraction so far away from application it’s only interesting if you love math for math’s sake or (far more often) you’ve already been programming on your own.
They generally start at a level of abstraction so far away from application it’s only interesting if you love math for math’s sake or (far more often) you’ve already been programming on your own.
Starting with weeks of “Let’s add and subtract binary numbers for reasons you’ll understand later,” or even, “Your terminal can do math, also here’s a for loop” is only interesting if you have already been building things, have a neurodivergent personality, or take stimulants.
A couple schools have figured this out.
Starting with, “Let’s build something that will be crappy for reasons you don’t understand yet” or even “this code will let you solve these puzzles” is substantially better than “How do you make logic gates for transistors?”
Starting with, “Let’s build something that will be crappy for reasons you don’t understand yet” or even “this code will let you solve these puzzles” is substantially better than “How do you make logic gates for transistors?”
The average response when I show a professor our curriculum is, “Oh pish posh, you can’t build an application without understanding fundamentals of computing!”
You totally can. And *then* you learn what’s under the hood! And it makes learning that 1000x easier.
You totally can. And *then* you learn what’s under the hood! And it makes learning that 1000x easier.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
