And then: You gotta convince folks that AI is not going to replace entire teams, that you still need folks to know what the system should ultimately do (at a technical level), but it doesn't make sense to treat it like blasphemy or learned ineptitude. It's a new dimension. That's all. (n=6)

With raw programming work now being offloaded, the ability to design good systems is going to be of paramount importance for even a new grad engineer going forward (Would you ever hire a code monkey army?) What would future interviews look like? What would your day job be as a new grad? (5/n)

I've seen AI generate some really good code, and some garbage that could be a toxic biohazard. However, if I tracked what it did, was repeatedly checkpointing stuff and correcting it (manually or through a prompt) I found the cognitive load of writing code being shifted towards the design. (4/n)

It's like nitrous in NFS, I guess. It should augment your workflow, not replace it. Do what you were doing before. Think, design the same way, whatever. Offload mundane tasks to it. Or ask it to automate operational, maintenance tasks for you. (3/n)

Should you consider it an ever-growing and important part of your workflow? Yes. It's like fire, or an attack dog. You have to control it, guide it, keep an eye on it... but in the end it does have real value. Just don't become too dependent on it and offload your thinking, lest you lose it. (2/n)