This "problem" is pathological and those selling solutions are misleading those who buy into it.
Software engineering often isn't just answering "how" to accomplish something, but also all the five other questions starting with 'w'. Software ate the world a very long time ago, so people being allergic to code while trying to run a business is only sounding more and more absurd as time marches on.
What are we really trying to solve for here? All that could be automated reasonably well has been already. In most cases you do not want a stochiastic result, but exact code to be reused. We use libraries in our code and we have reproducibility of results. The code that needs to be written for most applications is minimal and only grows large as the business refines what they want. This code is unique and virtually worthless to any other business. The code mirrors the organization. We already know all this for decades. It's very confusing to me to keep hearing about this insistence that we need to automate software engineering.
I suspect several wannabe billionaires couldn't write code even if their life depended on it, which explains why they're so enthusiastic about AI. And why they have been so enthusiastic about every other broken promise about replacing developers that came before it.
> Software ate the world a very long time ago, so people being allergic to code while trying to run a business is only sounding more and more absurd as time marches on.
I don't agree with this at all. Part of the pitch of code is packing really nasty semantics into a single interface. This inherently reflects in the services we provide to clients. This interface should naturally correspond to UI, if that's what you offer. If you can only express the interface for your service in code, you've failed.
Unless of course you primarily operate a code-centric product, like an sdk.
If your car can't be owned and operated by someone with zero knowledge of how cars work you've failed. And yet to this day every car owner is aware that their lack of any such knowledge would/does cost them dearly at the mechanic and at the dealership too. And of course mechanics and car salesmen love to see such clients coming their way.
Yea, I mostly agree with this. Consumers tend to have some sort of understanding of the car market. If you can't cater to them, you've failed.
Correspondingly, it's very easy to imagine someone disgruntled for having to deal with code (i imagine hotwiring a car in the context you provided). People know their lane; you can't force them to change it.
I think you might be missing the point. The barrier to entry has been and will continue to be the ability to operate that business or pay others to do so. Business is a competitive space, so why would it be easy? And when it is, what's the catch?
Software engineering often isn't just answering "how" to accomplish something, but also all the five other questions starting with 'w'. Software ate the world a very long time ago, so people being allergic to code while trying to run a business is only sounding more and more absurd as time marches on.
What are we really trying to solve for here? All that could be automated reasonably well has been already. In most cases you do not want a stochiastic result, but exact code to be reused. We use libraries in our code and we have reproducibility of results. The code that needs to be written for most applications is minimal and only grows large as the business refines what they want. This code is unique and virtually worthless to any other business. The code mirrors the organization. We already know all this for decades. It's very confusing to me to keep hearing about this insistence that we need to automate software engineering.