commenter-thread

One of the big ways you can tell that a job is not as necessary as the worker thinks is when the worker starts doing their job shitty on purpose in order to stop a machine from replacing them.

There used to be entire departments of engineers whose entire career was "draw pictures of things". That's what they did, and they were very good at it, and I'm sure that if you asked them they'd have all kinds of reasons why you could never automate their job.

And yet I've got a drafting module in my CAD software, and it draws the pictures of things. And it is up to me to design the things, and to identify what pictures of them are needed and what numbers to put on the pictures, but that entire department of people who turned "give me a picture of the part in thus-and-so orientation" into marks on paper has been replaced by a half-dozen mouse-clicks.

eh. I'm pretty sure that we were doing that kind of thing with Markov chainers back in the 90s; we've learned to write grammar rules expansive enough (and gotten processors fast enough) that the thing can chain on syntax rather than just vocabulary.

Which, that's interesting, but I don't think it's a "we've given birth to aye-eye" moment.