First I’d like to put this into the actual reality context where the following applies:
-
In my own experience, most of the time spent today (say, when building a full featured multi-tenant Phoenix LiveView app) is not being spent on coding or even designing the system, but in (no particular order) on brainstorming, designing UX, defining visual standards, sensing the user needs, live-testing, capturing of and reasoning about the user feedback, and yes, marketing the product, all being workflows that are not even technical.
-
Since it would be borderline insane to delegate the said stakeholder responsibilities to an LLM, and since the technical part is definitely not the bottleneck (but could easily become as a result of an artificial “creativity”/automatic code generation), why would one even invest into optimizing that what’s not the problem in the first place?
-
The sheer notion that there are enough (human) resources to a) devise a large enough number of business use cases/opportunities and b) be capable of filling up an enormously parallel agentic enterprise with articulated requirements is laughable.
In short, if the idea is to produce something that generates revenue once deployed, developing it is the least of all concerns.
