[bee_rider]

I think this is probably because interesting jobs require handling information, which computers are good at, and boring ones require just shuffling stuff around in the physical world, which computers are still mediocre at.

But, designing a robot that can do tedious tasks is an intellectual job, just a really hard one. If we automate intellectual jobs to the point where, like, any random team of 10 people with engineering degrees can make a really good robot, I guess we should see the tedious jobs taken too.

[yowzadave]

I used to work as an architect. As far as I am aware, AI/automation has so far only made inroads in the earliest "concept" phases--image-making, concept massing, conceptual space-planning, etc. That is only the first, shortest, and most creative part of designing a building. After the concept design has finished, there are longer and more expensive phases of design development and construction drawing that still require huge amounts of coordination between the various design/construction professionals & stakeholders. At this phase, the work is much more practical: adding detail to the drawings reveals that, say, the size of the required mechanical units exceed the area that originally been allocated to them in the concept phase, and the architect will need to work with the structural engineer/mechanical engineer/client/etc. to modify the solution so that the building still works. It's this latter phase of drawing/coordinating/redrawing that has so far been very resistant to automation.

I would still call this part of an architect's job "intellectual work". My guess is that it hasn't been automated because it requires deep domain knowledge in multiple areas...knowledge which your typical AI software person doesn't have.