> It may be that like clothes, there's only so much need for software.
Clothing demand has increased greatly in the past decade due to fast fashion. Much of this clothing is designed to cost a few bucks, last a few wears, then get thrown out. It's an ecological disaster.
Maybe we'll see something similar happen with software — as production costs fall, trends will shift toward few-use throwaway software. I highly suspect this is already happening.
Sorry I meant -- only so much demand for people to produce clothing. the thesis "AI will not replace software engineers" could go the same way as textiles (or not). Massive demand for software, no need for developers. Same as I'm sure having AI art will probably increase the total consumption of art/music, but probably reduce the jobs for artists.
I don't know, hopefully not much! Just reading the article about IDEs using one version of typescript and builds using another, along with some incompatibilities. It raises concerns there will be some hiccups with various dev tools.
You would need to rerun the LLM, but you wouldn't necessarily need to rebuild the codebase from scratch.
You can provide the existing spec, the new spec, and the existing codebase all as context, then have the LLM modify the codebase according to the updates to the spec.
But that's just an identifier which you can easily update when you move, like a domain=>IP mapping? Businesses still have your physical address.
A system where they didn't get our address at all would be great but I think we would also need alternative payment providers that don't share any billing-related address information with the business.
Clothing demand has increased greatly in the past decade due to fast fashion. Much of this clothing is designed to cost a few bucks, last a few wears, then get thrown out. It's an ecological disaster.
Maybe we'll see something similar happen with software — as production costs fall, trends will shift toward few-use throwaway software. I highly suspect this is already happening.
reply