SLOP3733: Turning Every Course You Take Into a Game

Putting 130 hours into a game is easy. Putting 130 hours into a course is not, and it is the same hours and the same person. The difference is how fast the reward arrives. Learn to build that reward, and finish a course the way you finish a game.

• game mechanics
• study design
• motivation

Why one of these is easy and the other is not

Nobody needs discipline to put 130 hours into League of Legends. You do not plan it, you do not force yourself, you queue again. Put the same 130 hours into a course and it is grim: you sit down, you struggle, and most evenings you cannot say what moved.

Same hours. Same person. What differs is how fast the work pays you back. A game tells you constantly whether you are getting anywhere. A course tells you in three weeks, in red pen.

So the whole course is one practical question: can you build that reward for yourself, and finish a course the way you finish a game — one step at a time, absorbed, and without it costing you everything you have?

Two kinds of game answer two different halves of it, and they are not interchangeable.

Part one — making every minute worth using

You sit down for half an hour. Or an hour, or a whole morning, or a whole day. It is painful, you cannot get into it, and at the end of it almost nothing has advanced. Everyone knows this state and nobody schedules it.

A MOBA never once lets it happen. Minions arrive every thirty seconds and each one is worth gold if you take it cleanly. Leaving your lane costs a known amount and might buy a kill somewhere else. Dragon and herald spawn on a clock the whole map can see. There is never a minute in which the right thing to do is nothing, and you always know what this minute is for.

That is what weeks 2–5 are for. Not to admire the design — to take it apart and build the same thing over your own thirty minutes, so that every minute of a sitting is a minute you can use.

Part two — how to start something far too hard

A Souls game is not a forty-minute match. It is a wall of bosses, and the first time you meet one you die in a minute or two.

Everyone reads that as cruelty, and the causation runs the other way:because the boss is hard, you die in ninety seconds, so you find out you were wrong ninety seconds after starting. Being hard is what makes the feedback fast.

Ninety seconds is also only long enough to remember one thing — it always sweeps after the second swing— and then you think if I fix just that one thing, do I get through? You are already walking back in. You did not decide to be brave and you did not talk yourself into it; you wanted to know the answer.

Compare that with a fighting game, which asks you to love it first: drill a combo against a dummy, learn the frame data, and find out days later in a real match whether any of it was worth the hours. That works for people who already love the game. A Souls game asks for something everybody has.

Twenty attempts later the boss is dead and you never planned anything. The impossible task broke itself into small ones, a lesson at a time, because the loop was short enough to only carry one.

That is weeks 6–9: how to get started on something too hard to start, and how to make a thing that big become a thing that small. No ladder gives you this, however well you build it.

Part three — the run

Weeks 10–12 you point both at the course you stalled on — the one you started, stopped, restarted and stopped again, and still believe you need. You cover a quarter of it in about thirty hours and sit an exam we set on the part you chose. Everything else you hand in is something you wrote about yourself. That one isn’t.

The same claim, in numbers

All of it rests on one measurable thing: how long you work before you find out whether it worked. Over a fixed 130 hours, that interval decides how many chances you get.

A Souls boss gives you fifteen hundred times as many as an assignment does. That is the entire reason one of them is easy to spend a hundred hours on.

Everything from week 2 onwards is about moving yourself leftward along this.

Who it is for

Anyone who has watched a semester go past without being able to say what they did with it, and anyone carrying a subject they keep starting over. There are no prerequisites and the reading is light, but this is not a soft course: you will play two demanding games attentively, ship a mechanism that survives you being tired, and then go back to something you have already failed to get through.

You do not need to write code. Two of the three assessments offer a paper route and a built route, marked identically, and a paper system in daily use beats an unfinished program every time.

Where to go next