I would propose boundaries that align partly with how I perceive the weather, and partly with how we plan our year (by months): Summer starts June 1st, Fall starts September 1st, Winter starts December 1st, and Spring starts March 1st.
1,672 karma · joined June 18, 2020
I would propose boundaries that align partly with how I perceive the weather, and partly with how we plan our year (by months): Summer starts June 1st, Fall starts September 1st, Winter starts December 1st, and Spring starts March 1st.
It's fine to be concerned, but this kind of take is why public agencies are damned no matter what they do. In the private sector, operating with the suboptimal resources you have while working on a better iteration is standard practice, even in industrial settings. But when you're a public organization, if anyone can find anything that is less than 100% optimal, the same people who complain about how slow the public sector is will complain that you're cutting corners, or that you're inept.
Funny... seems like about half of devs think AI writes good code, and half think it doesn't. When you consider that it is designed to replicate average output, that makes a lot of sense.
So, as insulting as OP's idea is, it would make sense that below-average devs are getting gains by using AI, and above-average devs aren't. In theory, this situation should raise the average output quality, but only if the training corpus isn't poisoned with AI output.
I have an anecdote that doesn't mean much on its own, but supports OP's thesis: there are two former coworkers in my linkedin feed who are heavy AI evangelists, and have drifted over the years from software engineering into senior business development roles at AI startups. Both of them are unquestionably in the top 5 worst coders I have ever worked with in 15 years, one of them having been fired for code quality and testing practices. Their coding ability, transition to less technical roles, and extremely vocal support for the power of vibe coding definitely would align with OP's uncharitable character evaluation.
On the pro-AI side, people are conflating technology success with product success. Look at crypto -- the technology supports decentralization, anonymity, and use as a currency; but in the marketplace it is centralized, subject to KYC, and used for speculation instead of transactions. The potential of the tech does not always align with the way the world decides to use it.
On the other side of the aisle, people are conflating the problematic socio-economics of AI with the state of the technology. I think you're correct to call it a failure of PMF, and that's a problem worth writing articles about. It just shouldn't be so hard to talk about the success of the technology and its failure in the marketplace in the same breath.
What will it mean if the cutting edge models are open source, and being OpenAI effectively boils down to running those models in your data center? Your business model is suddenly not that different from any cloud service provider; you might as well be Digital Ocean.
My ranking from most evil to least would be:
1. Google
2. Meta
3. Microsoft
4. Amazon
5. Apple
6. Netflix