My rational as to why this is a good thing in general was and remains a focus on generating consumer surplus, it’s this surplus which we as a people derive our wealth. The hope was that the surplus would be sufficient to cover the loss of those that lost their jobs, either in wealth redistribution or in new opportunities.
What’s different this time is productivity increases are not being met with an increase in demand. This will drastically increase inequality and to a lesser extent civil unrest, and I think both are destructive. I think financialization of the economy did greater damage, and the combination of both is going to really suck. I would prefer we keep productivity improvements and reverse the financialization even if that means pensions are decimated - they are probably going to be decimated anyway. Better to do it in a way that causes less damage.
I am more productive using it, but that is just me.
I know there is a lot of hype about LLM's and I'm genuinely interested in the niches that they can fill, and where they definitely shouldn't be involved in the software development process.
I would say I'm an expert level programmer in the small field that I work in, and have set up development teams in the past.
I think that is an advantage to working with integrating LLMs into a dev cycle as I have experience in providing structure with developers, something that LLMs 100% require, without a shred of doubt.
As the capability of LLMs continues to grow, having some framework around where they are 'almost good enough' will help re-evalutate them as they improve.
I'm not trying to prove anything to anyone else, just build a reference point for where we are now.