Generative-AI powered programming is the ``fast fashion'' movement equivalent for software development. People aren't interested in paying more for something that is future-proof when they can pay exponentially less for something that satisfies their needs now, and to replicate that process again if they need to update the feature set.There's quite a bit to unpack here, so let me step through this a bit more carefully.
It all goes back to the capitalistic mode of operation. In the beginning, clothing was made coarsely at the individual level. For the fancier stuff, one would head to the tailor for something that fits better. Eventually many wanted fancier stuff, and a market for it was created, which incentivises leveraging economics of scale to build factories to churn out decent quality clothes at an affordable price.
But clothes have a shelf-life that is independent of utility---no one wants to look dated with clothes that are otherwise functional. So the capitalism evolves into hyper-capitalism with extreme consumerism, with clothes that are designed to be much cheaper through reducing durability, but with the advantage of being faster to evolve as tastes change.
This is the fast fashion we are talking about.
People still wear fancy suits and dresses, and the tailors are still being approached for that. But this is not the norm for the large variety of people over most of the time.
Translating the analogy over, software used to be bespoke, with proper requirement gathering steps, followed by development, before undergoing testing to validate fit-for-purpose. Old computer systems were unique enough that software was truly bespoke to the architecture---the gradual rise of standardised platforms that come from leveraging economics of scale and Moore's Law made creating common software libraries to abstract out the bespoke parts a major pathway towards writing one source code, but cross-building to more than one operating system.
Then the web-browser became an even greater unifier that went across hardware and operating system, and everyone started building software on that as a platform. The old web relied on the open-ness of reading source files loaded into the web-browser to spread ideas, and the content-distribution network (CDN) invention took standardisation to a whole new level. The rise of the smartphone made ``app-ification'' a real thing, and many are conditioned to demand an ``app'' for even the simplest things that an web-browser-run page could handle.
Software development then started to hit the hyper-capitalism and extreme consumerism phase.
This was also aided by first the so-called Agile methodology that favoured rapid iterative prototyping over formalised design over a shortened time frame of two weeks or so instead of ``when it is done'', and now by the power of generative-AI that allegedly reduces the gap between the user who wants the functionality, and the ability to achieve those.
Kind of like how ``typist'' and ``letter writer'' are no longer legitimate jobs now, because almost everyone knows how to operate a [computer] keyboard, as well as communicate with each other over on-screen text/audio-visual teleconferencing/email in their favourite language of choice.
So in some real way, the rise of generative-AI does change the nature of software development; it prioritises and promotes the ``fast fashion'' style of doing things, arguing that maintainability is not important since the entire software can be re-written through appropriate prompts that includes the new featurers in it.
After all, if we are truly following the philosophy of being outcome driven, why then should anyone be harping about the nature of the source code?
Of course there are still uses for bespoke software, but this is likely to be something that only a small population and/or niched one will truly care about. For the rest, something quick and dirty can be concocted with generative-AI with little effort for near-immediate use by anyone. The ease of access to the generative-AI also obviates the need for code hygiene sensu change request handling/feature adding.
Depressing? I don't know. I always have a saying to myself that I freely share:
Never do something that a fourteen-year-old can do for a job if one can; that's not where one's true value lies.Fourteen-year-olds have more time than life experience on their hands, and epitomise what I think is the best representative of naĂŻve brute force approaches. I know because I was fourteen once, and had the drive to grind things out to inexorably change my life forever.
Anyway, that's all for now. Fast fashion, or bespoke tailor---which end of the spectrum is the most lucrative then?