That's noted further down the page:

- `_*` = any string

Bring back Pebble Steal. I lost my original and got the pebble time 2 but its just not the same.

> Why have grades at all? Instead, have a directed graph of skills that you need to advance through

FTA: "Elements of so-called equitable grading, which is supposed to be more resistant to bias than traditional grading, have taken off in American schools. Roughly 40 percent of middle-school teachers work in schools where there are no late penalties for coursework, no zeroes for missing coursework, and unlimited redos of tests."

> It would remove the stigma of "being held back", as there are no levels in a strict sense, just cumulative progress

These students do worse. Absent a challenge, you get the pedagogical equivalent of button mashing. Evaluation is a necessary component of progress. It seems that if the evaluation is stripped of consequence, it ceases to evaluate.

How much math is in a typical CS program these days? Calc 1-3 (maybe 3, varied by school), Linear Algebra, Statistics (inconsistent across programs), Discrete were pretty much it when I was in school 25+ years or so ago. That's only 4-6 courses depending on the university, though some where the CS dept was more strongly associated with an engineering college might have added Diff Eq and others. (I got interested in CS education and reviewed a lot of curricula in the US at the time, this is from memory.)

Some schools like MIT might have required more, but on average what I wrote was about it. Has it increased since then? Based on the new hires I've seen the last decade I'd have guessed the math requirements were mostly the same.

I don’t agree it’s a structural VS nominal difference. Typescript is structural, but it does have the “implements” keyword.

Which makes a million times more sense to me, because realistically when do you ever have a structure that usefully implements an interface without being aware of it?? The common use-case is to implement an existing interface (in which case might as well enforce adherence to the interface at declaration point), not to plug an implementation into an unrelated functionality that happens to expect the right interface.

    interface Foo {
        name: string
    }

    class One implements Foo {
        constructor(public name: string) {}
    }

    class Two {
        constructor(public name: string) {}
    }

    function test(thing: Foo): void {
        //...
    }

    test(new One('joe'));
    test(new Two('jane'));