The number of devs I've worked with who can't touch-type and don't use or know their way around a proper IDE is depressingly large.

If you are trying to sell it, you are doing a poor job and effectively siding with OP while desperately trying to write the opposite.

Juniors are mostly better than what you write as behavior, I certainly never had to correct as much after any junior as OP writes. If you have 'boring code' in your codebase, maybe it signals not that great architecture (and I presume we don't speak about some codegens which existed since 90s at least).

Also, any senior worth their salt wants to intimately understand their code, the only way you can anyhow guarantee correctness. Man, I could go on and on and pick your statements one by one but that would take long.

You've come full circle and are essentially just describing what the OP was saying in their initial post lol.

I don't believe that investing more of my time in a slower process now would result in an advantage if that other process was refined. I've toyed around with these tools and know enough to get an environment up and running so what would I gain from using them more right now if those tools may significantly change before they're adapted to more efficient usage?

I'm okay not being at the bleeding edge - I can see the remains of the companies that aggressively switch to the new best thing. Sometimes it'll pay off and sometimes it won't. I am comfortable being a person that waits until something hits a 2.0 and the advantages and disadvantages are clear before seriously considering a migration.

If you don't do it yourself and you don't get overtaken by AI, you've lost the head start to be better next time - humans learn, and they atrophy as well.