When we created cars that replaced buggies, that came with new machines for manufacturing, who need mechanics. The same for most physical automation. When we automated pen and paper business processes with SaaS, we created new managment positions, and new software jobs. LLMs don't create anything new, they simply replace human computer i/o, with tokens. That's it, leaving the humans who are replaced to fight for a li…
I'm not worried about AI job loss
181–190 of 582 posts
Re: I'm not worried about AI job loss
#182Maybe I am wrong, but the history of business on the web says I am right. If you go back and look at why those businesses think they are successful, and if that analysis is correct, then I am.
Re: I'm not worried about AI job loss
#183When we created cars that replaced buggies, that came with new machines for manufacturing, who need mechanics. The same for most physical automation. When we automated pen and paper business processes with SaaS, we created new managment positions, and new software jobs. LLMs don't create anything new, they simply replace human computer i/o, with tokens. That's it, leaving the humans who are replaced to fight for a li…
You are thinking too linearly. When the price of goods and services go down because the cost to produce those goods are services decreases, that means things are cheaper. Now that things are cheaper we have more money to spend on other goods or services.
Who knows what industries will be created because of this alleged release of human labor.
When the refrigerator was invented we didn’t just replace an industry of shipping ice, we created new industries that relied on refrigeration. That’s creative destruction. That’s economic growth.
This is not to mention that I find the scope and scale of AI displacement to be highly dubious and built on hype.
Re: I'm not worried about AI job loss
#184Re: I'm not worried about AI job loss
#185When we created cars that replaced buggies, that came with new machines for manufacturing, who need mechanics. The same for most physical automation. When we automated pen and paper business processes with SaaS, we created new managment positions, and new software jobs. LLMs don't create anything new, they simply replace human computer i/o, with tokens. That's it, leaving the humans who are replaced to fight for a li…
What DOES go up with automation is demand. Fewer farmers today than 100 years ago, but significantly more mouths to feed.
What also increases is new kinds of jobs; entirely new fields. The automobile shrank the number of buggy whip makers, but taxi drivers increased. Then the internet increased Uber drivers on top of taxi drivers.
Re: I'm not worried about AI job loss
#186I was with the author on everything except one point: increasing automation will not leave us with such abundance that we never have to work again. We have heard that lie for over a century. The stream engine didn't do it, electricity didn't do it, computers didn't do it, the Internet didn't do it, and AI won't either. The truth is that as input costs drop, sales prices drop and demand increases - just like the parad…
If you want to live with no electricity, no running water, and a lack of refrigerated food, you could do so purely on welfare. In that sense, we already have the UBI that Marx predicted. However, most people want fruits and vegetables instead of getting rickets, goiter, and cholera from an 1800s diet. Many are even willing to work 80+ hours a week to do so.
Re: I'm not worried about AI job loss
#187Whenever I get worried about this I comb through our ticket tracker and see that ~0% of them can be implemented by AI as it exists today. Once somebody cracks the memory problem and ships an agent that progressively understands the business and the codebase, then I'll start worrying. But context limitation is fundamental to the technology in its current form and the value of SWEs is to turn the bigger picture into a…
"The steamroller is still many inches away. I'll make a plan once it actually starts crushing my toes." You are in danger . Unless you estimate the odds of a breakthrough at <5%, or you already have enough money to retire, or you expect that AI will usher in enough prosperity that your job will be irrelevant, it is straight-up irresponsible to forgo making a contingency plan.
Re: I'm not worried about AI job loss
#188Earlier quoted context omitted.
A lot of this can be provided or built up by better documentation in the codebase, or functional requirements that can also be created, reviewed, and then used for additional context. In our current codebase it's definitely an issue to get an AI "onboarded", but I've seen a lot less hand-holding needed in projects where you have the AI building from the beginning and leaving notes for itself to read later
Curious to hear if you've seen this work with 100k+ LoC codebases (i.e. what you could expect at a job). I've had some good experiences with high autonomy agents in smaller codebases and simpler systems but the coherency starts to fizzle out when the system gets complicated enough that thinking it through is the hard part as opposed to hammering out the code.
In my case the AI is actively detrimental unless I hand hold it with every single file it should look into, lest it dive into weird ancient parts of the codebase that bear no relevance to the task at hand. Letting the latest and "greatest" agents loose is just a recipe for frustration and disaster despite lots of smart people trying their hardest to make these infernal tools be of any use at all. The best I've gotten out of it was some light Vue refactoring, but even then despite AGENTS.md, RULES.md and all the other voodoo people say you should do it's a crapshoot.
Re: I'm not worried about AI job loss
#189Re: I'm not worried about AI job loss
#190Earlier quoted context omitted.
As long as the owner class can leverage, "Hey, that {out group} is sitting around doing nothing and getting free money!" we'll never have anything close to UBI imo.
[flagged]