Earlier quoted context omitted.
Someone asked “where are all the small businesses”, this was a reply to that. Small businesses don’t have entire art departments.
Gotcha, so the impact of AI is small businesses get to save a couple hundred dollars and the cost is only 2% of your countries GDP. That’s good.
AI adoption and Solow's productivity paradox
201–210 of 783 posts
Re: AI adoption and Solow's productivity paradox
#202Re: AI adoption and Solow's productivity paradox
#203Just to be clear, the article is NOT criticizing this. To the contrary, it's presenting it as expected , thanks to Solow's productivity paradox [1]. Which is that information technology similarly (and seemingly shockingly) didn't produce any net economic gains in the 1970's or 1980's despite all the computerization. It wasn't until the mid-to-late 1990's that information technology finally started to show clear benef…
One part of the system moving fast doesn't change the speed of the system all that much. The thing to note is, verifying if something got done is harder and takes time in the same ballpark as doing the work. If people are serious about AI productivity, lets start by addressing how we can verify program correctness quickly. Everything else is just a Ferrari between two traffic red lights.
Re: AI adoption and Solow's productivity paradox
#204Earlier quoted context omitted.
It’s also pretty wild to me how people still don’t really even know how to use it. On hacker news, a very tech literate place, I see people thinking modern AI models can’t generate working code. The other day in real life I was talking to a friend of mine about ChatGPT. They didn’t know you needed to turn on “thinking” to get higher quality results. This is a technical person who has worked at Amazon. You can’t expec…
> I see people thinking modern AI models can’t generate working code. Really? Can you show any examples of someone claiming AI models cannot generate working code? I haven't seen anyone make that claim in years, even from the most skeptical critics.
Re: AI adoption and Solow's productivity paradox
#205Yeah, if your Fortune 500 workplace is claiming to be leveraging AI because it has a few dozen relatively tech illiterate employees using it to write their em dash/emoji riddled emails about wellness sessions and teams invites for trivia events… there’s not going to be a noticeable uptick in productivity.
The real productivity comes from tooling that no sufficiently risk adverse pubco IS department is going to let their employees use, because when all of their incentives point to saying no to installing anything ever, the idea of giving the permissions required for agentic AI to do anything useful is a non-starter.
Re: AI adoption and Solow's productivity paradox
#206Workers may see the LLM as a productivity boost because they can basically cheat a their homework. As a CEO I see it as a massive clog up of vast amounts of content that somebody will need to check. A DDoS of any text-based system. The other day I got a document of 155 pages in Whatsapp. Thanx. Same with pull requests. Who will check all this?
Re: AI adoption and Solow's productivity paradox
#207Earlier quoted context omitted.
In a WhatsApp group full of doctors, managers, journalist and engineers (including software) in age of 30-60 I asked if anyone heard of openclaw and only 3 people heard of it from influencers, none used it. But from my social feed the impression was that it is taking over the world:) I asked it because I am building something similar since some tome and I thought its over they were faster than me but as it appears th…
> I asked it because I am building something similar since some tome and I thought its over they were faster than me If you have been working on a usecase similar to OpenClaw for sometime now I'd actually say you are in a great position to start raising now . Being first to market is not a significant moat in most cases. Few people want to invest in the first company in a category - it's too risky. If there are a cou…
On my app the tech is based on running agent generated code on JavaScriptCore to do things like OpenClaw, I’m wrapping the JS engine with the missing functionality like networking, file access and database access so I believe I will not have a problem with releasing it on Apple AppStore as I use their native stack. Then since this stack is also OS, I’m making a version that will run on Linux, the idea being users develops their solution on their device(iOS&Mac currently) see it working and and then deploys on a server with a tap of a button, so it keeps running.
Re: AI adoption and Solow's productivity paradox
#208Re: AI adoption and Solow's productivity paradox
#209Just to be clear, the article is NOT criticizing this. To the contrary, it's presenting it as expected , thanks to Solow's productivity paradox [1]. Which is that information technology similarly (and seemingly shockingly) didn't produce any net economic gains in the 1970's or 1980's despite all the computerization. It wasn't until the mid-to-late 1990's that information technology finally started to show clear benef…
It’s also pretty wild to me how people still don’t really even know how to use it. On hacker news, a very tech literate place, I see people thinking modern AI models can’t generate working code. The other day in real life I was talking to a friend of mine about ChatGPT. They didn’t know you needed to turn on “thinking” to get higher quality results. This is a technical person who has worked at Amazon. You can’t expec…
Re: AI adoption and Solow's productivity paradox
#210Earlier quoted context omitted.
> I see people thinking modern AI models can’t generate working code. Really? Can you show any examples of someone claiming AI models cannot generate working code? I haven't seen anyone make that claim in years, even from the most skeptical critics.
I've seen it said plenty of the times that the code might work eventually (after several cycles of prompting and testing), but even then the code you get might not be something you'd want to maintain, and it might contain bugs and security issues that don't (at least initially) seem to impact its ability to do whatever it was written to do but which could cause problems later.