"Writing code and building products" isn't engineering.
I think it's true that making software has gotten more accessible. That's been happening for a long time. I remember the whole deal about "low code and no code platforms are going to make software engineers obsolete", and that never happened. Various platforms offered tools for non-developers to work with data and build integrations, but the most complex work still required people with expertise in design and testing.
Someone like Samuel Florman would probably point out the social responsibilities that come with engineering, Henry Petroski would talk about how the people who are using AI tools and "vibe coding" don't have an understanding of edge cases and failure, and Eugene Ferguson would talk about how AI tools create a gap between prompts and design in the mind's eye. People with different takes on what it means to do engineering would find that an engineer can use AI tools in their work, but creating software with an AI tool isn't inherently engineering.
Jokes aside, I think you’re valid but if you take the macro view, it’s clear that there are now more people doing some form of engineering, the same way the digital camera led to more people doing photography, and so on.
I think we can make separate distinctions around the act of consuming vs creating—a lot of vibe coding is beginning to look more like “consuming software” but that’s not what I was intending to describe here.
"Writing code and building products" isn't engineering.
I think it's true that making software has gotten more accessible. That's been happening for a long time. I remember the whole deal about "low code and no code platforms are going to make software engineers obsolete", and that never happened. Various platforms offered tools for non-developers to work with data and build integrations, but the most complex work still required people with expertise in design and testing.
Someone like Samuel Florman would probably point out the social responsibilities that come with engineering, Henry Petroski would talk about how the people who are using AI tools and "vibe coding" don't have an understanding of edge cases and failure, and Eugene Ferguson would talk about how AI tools create a gap between prompts and design in the mind's eye. People with different takes on what it means to do engineering would find that an engineer can use AI tools in their work, but creating software with an AI tool isn't inherently engineering.
No true Scotsman uses AI? :)
Jokes aside, I think you’re valid but if you take the macro view, it’s clear that there are now more people doing some form of engineering, the same way the digital camera led to more people doing photography, and so on.
I think we can make separate distinctions around the act of consuming vs creating—a lot of vibe coding is beginning to look more like “consuming software” but that’s not what I was intending to describe here.
By your logic: people who use calculators are mathematicians