@mhoye Ooof, this is very close to what I studied at...

@mhoye Ooof, this is very close to what I studied at university!

I would *not* teach coding and related architecture or methodology. They can learn that elsewhere.

Instead, you could explore why the tech world is the way it is. Looms, punch cards, Babbage/Lovelace. @JamesGleick ’s “The Information”. Shannon and Turing for compsci theory.

Lessig’s “Code is Law” + an intro to FOSS for practice. Top it off with @timnitGebru ’s stochastic parrots.

Like 14 March at 19:27 | Wall-to-wall | Open on chaos.social

2 comments

mhoye

@slothrop @JamesGleick @timnitGebru

That's a lot for the "first year, here's the language/history/perspectives you will need to navigate this industry as a moral actor" thing I'm going for, though "at a bare-assed minimum let's not bullshit ourselves about what AI tools are, who they serve and how they work" belongs in there.

Code Is Law though does not. The central thesis of "Code Is Law" just... isn't true. At all. It's so profoundly not-true that it's weird anyone ever though otherwise.

14 March at 20:21 | Open on mastodon.social

Central Illumination Agency

@mhoye I agree that Code is Law didn’t quite live up to its own hype.

But the central postulate - that software imposes rules, and it’s way harder to break those rules than it is to break laws in the physical world, and that difference makes a difference - remains true.

14 March at 20:26 | Open on chaos.social