Discussion about this post

User's avatar
jeff's avatar
2hEdited

I swear there's not a econ/tech writer on the planet that has any idea what engineers actually do.

A software engineer is most importantly a *type of engineer*. And by and large engineers are people who define and solve problems. "Coding" is incidental to the job. It's like thinking mechanical engineers were all going to lose their jobs because CAD came along, after all, didn't they spend their days at a drafting table?

You keep mixing up the technological toolset of the job with, like, the actual substance of the job in this frustratingly reductive way.

I'm sympathetic, a bit, because there was this period of time where software engineers got a little high on their own supply and convinced themselves and everyone else that "coding" was this God-like skill set that was just *different* than everything else, and so I don't mind seeing them taken down a peg. But fundamentally coding was never engineering.

Peter Defeel's avatar

This does sound horrible. It’s also unlikely. More likely is the code reviewer or maintainer (to stick to coding) is a specialist who is needed when the AI messes up. I’m fairly dubious that coding has been replaced fully really - only the companies selling the AI are saying that, with the results we see from Claude recently.

Programmers aren’t, except for trivial apps, writing prompts like “build me an app to show a dog barking”, but instead getting AI to write what they could write themselves, with strong architectural inputs and frameworks and system knowledge.

More like pilots and auto pilots.

13 more comments...

No posts

Ready for more?