“Before AI I would have to study how Bluetooth works now I don't have to.”

And

“It's very good at handling the BS part of coding…”

This is the part that I think is difficult in a team situation.

Learning and understanding is the important part, and certainly isn’t BS.

I understand that it really can make it seem like velocity has increased when you really are shipping things that more or less “work”, but it’s really a good practice to understand your code.

I’ve had to spend a significant amount of time fixing work that was admittedly generated using AI by other engineers, and I really fear engineers are beginning to trade deep understanding for the high of getting something that “works” with little effort.

It might “work” but you might be ignoring the work everyone around you is doing to clean up your brittle code that doesn’t scale and wasn’t thought through at inception.