I’m a software engineer, and I’m not worried about AI taking my job. The shortest explanation of this is that “coding” is a very small part of what I do: there’s stuff that’s more product-related, and stuff that’s pre-paradigmatic (to stretch the term), and mentorship, and communication; when I do write code, a lot of the time the code itself is almost irrelevant compared to the concerns of integrating it into the larger system and making it easy to change or delete in the future when requirements change.
One stupid analogy here is that coding is like walking—important and potentially impressive if a machine does it, but insufficient on its own to actually replace a human in a job.
I’m a software engineer, and I’m not worried about AI taking my job. The shortest explanation of this is that “coding” is a very small part of what I do: there’s stuff that’s more product-related, and stuff that’s pre-paradigmatic (to stretch the term), and mentorship, and communication; when I do write code, a lot of the time the code itself is almost irrelevant compared to the concerns of integrating it into the larger system and making it easy to change or delete in the future when requirements change.
One stupid analogy here is that coding is like walking—important and potentially impressive if a machine does it, but insufficient on its own to actually replace a human in a job.