And once I started to look at it that way, I started seeing all these potential ways to use AI to do what I do now, only better and more easily. So I’m going to keep looking for opportunities and going after them. If I’m going down, I’m going down swinging.
> If it’s doomsday, it doesn’t matter whether I act as if it’s doomsday or if I look for opportunities. Either way I’m fucked.
There are different degrees of “being fucked”. Not everyone is disadvantaged the same in a doomsday scenario: it does not literally happen in a day and it does not necessarily spell doom for those who caused it or are outside their sphere of influence. It follows that someone who looked for alternatives rather than fully embracing the system might stand a better chance.
Furthermore, a scenario which is not yet inevitable may become so because people think it is inevitable and give up or act in a way that reinforces it. That’s the definition of a self-fulfilling prophecy.
Note I’m not advocating a specific approach to this case. My aim is to highlight that while the initial argument seems logically airtight, it is deeply flawed and you shouldn’t take it as the true solution.
If everyone acted like this all the time, there'd be no point in unionizing or voting. If you suspect it might be doomsday, you should join other people who feel the same and do something about it.
It's probably too late to stop it from filling the internet with misinformation and spam, but it's not too late to stop it from taking the jobs of the people who produced the training sets (i.e. writers, open-source coders, etc.)
Since the training data is sourced from the web and from users, I've been wondering how difficult it would be to collectively poison these systems with junk data. I'm guessing it wouldn't take that many people to do it.
Not saying one is harder than the other or criticizing anyone's skills, etc. Just looking at what the AI has available to learn from.
The goal of the “AI Ethics” professional class to have all AI be approved by well-compensated PhDs in corporate labs has always been a paternalistic farce.
Common people deserve access so they can figure out what their lives will be like now, and then we can make collective decisions about where we go.
> And that’s what a computer is to me. What a computer is to me is it’s the most remarkable tool that we’ve ever come up with, and it’s the equivalent of a bicycle for our minds.”
~ Steve Jobs
ChatGPT is motorcycles for our minds.
The more it serves us, the more indulgent, flaccid and incapable we will become. When our butler invitably degrades, we will have forgotten how to serve ourselves. At least with bicycles we were still pedalling.
Why should it? Any more than, say, the global economic system providing us with gasoline at the gas station, which we rely on?
BTW, animals do make tool. Even some insects (ChatGPT told me last night :)).
A motorcycle depends on, and thus is useless without, an external source of fuel.
> You know what’s pretty crazy? If you lean over on a motorcycle, it crashes. Don’t do that.
‐ Terry A. Davis, https://www.youtube.com/watch?v=Dwgj9UtuDFY
Today, if I want to be a programmer, I can procure all the equipment I need to do some serious programming -- for cheap! I have control over every step of the process. If creating software becomes something that you use AI to do rather than do yourself, it will require surrendering much of the process to mysterious cloud entities, like William Gibson's electronic voodoo gods floating out on the edges of cyberspace. Unless we have open-source-equivalent AI models that we can download, play with, run on our own hardware that actually give good results. I think I will wait for those to become available on hardware I actually have before faffing about with AI.
[0] https://twitter.com/StrongBadActual
[1] https://www.researchgate.net/figure/Then-a-Miracle-Occurs-Co...
> [Wozniak] was overjoyed when he learned that the skill that put so much effort into suddenly became massively easier. He wasn't worried about not being able to earn an above-average salary from this anymore, he was happy about all the new cool things he and everyone else would be able to build.
If you want to get things done, then having your skills obsoleted is good.
This is a nice idea, but in economic reality, you won’t be getting anything done if your boss lets you go.
* You don't know what a function is (or a method / class)
* You don't even understand variables, static types, bools/ints/strings
* You have no idea about an entry point such as main, how returns work
* You have no idea about OOO, organising code over multiple files
* You don't know what a socket is, you don't understand I/O, file handling
To top it all, code looks alien to you, you have no idea how to read it.
The only individuals who would be able to bridge the knowledge above, would likely become programmers anyhow.
* You don't have experience with basic technical decision making -- e.g. why would you pick Java vs. C vs. Python vs. Go vs. any other language, and how would that decision change if you were building a web app vs. mobile app vs. embedded software?
* You don't have a familiar set of tools and established preferences for the aforementioned decisions -- i.e. if an experienced programmer is building a web app, there are probably specific languages and tools they're inclined to reach for.
* You don't know about application deployment and productionization. How do you get your project somewhere people can use it? You don't know about deploying code to servers or running it in Docker or K8s or PaaS.
* You don't have the practiced logical thought process for things like algorithm design, debugging, figuring out user bug reports, identifying edge cases, predicting user behavior, etc.
* You don't have the experience with things that experienced programmers find "obvious" -- e.g. if you're building a web app, you need an authentication system, registration flow, password reset, etc.
I think the main effort to address this will be LLM-driven low-code solutions. Imagine something like Airtable, but with an integrated LLM assistant that can make changes to your app and write code to implement business rules and automation. This gets rid of problems like choosing your tech stack, deployment, etc. and it minimizes the amount of code the LLM has to create.
I imagine this will have effects comparable to those of spreadsheet software: non-programmers will be able to build custom tools with a newfound ease and some will end up learning a lot of programming skills in the process.
And, much like with spreadsheets, these tools will end up becoming business critical in unexpected ways and will turn out to be a huge pain in the ass to maintain. They'll find that parts of their business logic don't work as expected and that they can't figure out how to prompt the LLM to get it to implement the rules the right way. The users of these tools will basically have to learn some programming anyway or they'll have to hire experienced programmers to figure the problems out for them.
In 2019, this is sci-fi
In 2023, it can help engineers understand the complexity of taxes, translate some tax rules into code, help refine edge cases and fix mistakes.
In 2030, ???
Things move insanely fast lately. I would not bet on anything.Depending on the quarter only 10% to 25% of my time is writing code. The other is dealing with: finding high level reliability concerns, figuring out what solutions to implement, diving into complex acute production issues, evaluating trade-offs for fixes, finding ways to make things more efficient, negotiating what to prioritize with other teams/orgs/leadership, etc.
Could an AI do some of these things? Sure. Are they going to be able to figure out the right stakeholder to talk to, negotiate with them, get buy-in and decide on overall designs/solutions? No.
I'd be a bit concerned if I was a frontend developer (though any decent one could pivot to something else.) however.
It already has. Every single one of my coworkers is using Copilot. If you mean in terms of the job market, the shift to more declarative supervision of the tool rather than imperative implementation of the work yourself means that the bar for skill is far lower.
There will come a time when product managers and UX designers just use AI to generate Figma mocks, and AI generates an entire scaleable platform from just that. Will they need developers? Sure, but maybe 1. Certainly not 8-10.
The alternative would be built to help users leverage AI to do their taxes. Upload your docs and it’ll get you 90% of the way there or something like that. AI will help developers build that alternative faster. Almost every piece of software will need to be reimagined from the ground up in this way. That is the job security
> In particular, I started to realize that every little thing that we decide not to do as a company could have been done,
If every single company has more development bandwidth available, then at some multiple it would start driving demand and then wages down quickly. The multiple doesn't have to come just by AI improvements, as a lot of non developers can start using the AI to implement things.
It is very good if you intend to found a company, you have multiplied the things your company can do by leaps and bounds. Not so good for salaries developers.
At the rate this is developing, I can't help but think AIs will be designing smarter AIs within a decade or two. People reassure themselves that these AIs are just synthesizing the internet datasets -- that they don't have "souls". I would say that doesn't matter -- whether or not a submarine can swim, a race of advanced submarines could dominate the ocean.
I'm not fully convinced that the singularity requires intentionally designing a general AI, or that a glorified chatbot with some Darwinian forces applied to its existence couldn't get there.
People keep thinking The Matrix or I Have No Mouth But I Must Scream, but I just keep thinking Her -- that even a benevolent AI revolution means humans are pointless. Or worse, Bladerunner, since I'm quite sure that if we do create a general AI we'll still murder it after it answers 15 questions or steps out of line.
That anxiety is much harder to shake than the one about my job - I thought we had more time.
It's just a new tool. Just like when computers arrived, mathematicians were not replaced just because computers could do the calculations faster. When autotune arrived, artists were not replaced - they just added that to their repertoire.
Yes, some jobs will be lost. Yes, there will be a changing of the guards. That's just the nature of things - it's just how it's always been.
> Then at some point he describes his first time writing a game in software. He goes on about how running all the variations he tried in software would take a skilled engineer months of work, and he had done it in a couple hours - and was ecstatic.
I am sure everyone felt ecstatic at some point, regardless of their trade or field, when they worked on something all day or longer and got it done. The sheer joy it brings afterward makes your mind completely calm; past and future cease to exist for that moment. There are always going to be people like that.
AI or no AI, 20 years from now, people will still be writing software because it just makes them happy. Sure, the nature of problems will change, but these are the people who will keep pushing the field forward.
“I never think of the future - it comes soon enough.” - Grandpa Einstein.
And it also depends on the bad things that are coming, and what new things are going to come.
You are making an ethical argument based on utility, those two are not the best in combinations like that, the ethical argument should be made on an ethical foundation, not on the temporary outcome.
It's interesting how one of the most obvious problem spaces, the one of ethical reasoning is one that is least amendable to pure logic without adding a very large dose of humanity.
Example: killing is bad. But killing to save someone from endless misery (called Euthanasia) can be a good thing. But it still requires - where I live - two doctors to come to the conclusion that someone is beyond medical help and suffering needlessly. And then there needs to be a clear declaration on the capability of the person making the request that they are able to make such a request in the first place.
Ethics isn't simple, even in 'simple' cases.
Give it a year.
And they were on a relatively flat part of the tech curve…
Would be curious to hear from others that have read it, but I find it difficult to fault his core arguments (or at least what I interpret them to be).
The problem white collar humans have right now is that they're highly specialized. They're incredibly good at being very effective cogs. This is exactly what AI is getting so good at doing (in certain verticals). Traditional capitalism effectively demands that if a company can pay the owner of an algorithm 10% of what it would pay for a human to do the same thing (for even 80% of the quality), then that's what will eventually happen.
Can government regulate it? They can sure try, but then either the companies or AI hosting providers will move to a country that doesn't have the same restrictions and it will happen anyway.
Then people will say "it will just open up other industries". I'm not sure it will. What other industries will the swaths of copywriters, lawyers, accountants retrain for?
I just don't understand everyone saying "It's going to make everyone's lives easier". In the short term sure, but if AI gets to where it's owners want it to get to, then a lot of people are going to find themselves professionally worthless.
It's entirely possible that this is just not something we're prepared for, and it's almost guaranteed at this point that there's no stopping it.
What's really interesting is this book was released in 2016... and Yuval was using Microsoft's Cortana as the example of this upcoming AI...
Interesting times either way.
I'm hopeful.