...and saves humongous amounts of time in the process. Documentations are rarely a good read (however sad, I like good docs), and we should waste less engineering time reading them.
When a sector collapses and become irrelevant, all its workers no longer need to be employed. Some will no longer have any useful qualifications and won't be able to find another job. They will have to go back to training and find a different activity.
It's fine if it's an isolated event. Much worse when the event is repeated in many sectors almost simultaneously.
Why? When we've seen a sector collapse, the new jobs that rush in to fill the void are new, never seen before, and thus don't have training. You just jump in and figure things out along the way like everyone else.
The problem, though, is that people usually seek out jobs that they like. When that collapses they are left reeling and aren't apt to want to embrace something new. That mental hurdle is hard to overcome.
What if no jobs, or fewer jobs than before, rush in to fill the void this time? You only need so many prompt engineers when each one can replace hundreds of traditional workers.
The capitalists are failing to redeploy capital today. Thats why they have been dumping it into assets for years. They have too much capital and dwindling things they can do with it. AI will skyrocket their capital reserves. There is a poor mechanism for equalizing this since the Nixon years.
> They have too much capital and dwindling things they can do with it.
Yes, we've had full employment for a long, long time. But the idea here is that AI will free up labor that is currently occupied doing something else. If you are trying to say it will fail to do that, that may be true, but if so this discussion is moot.
As others in this thread have pointed out, this is basically what happened in the relatively short period of 1995 to 2015 with the rise of global wireless internet telecommunications & software platforms.
Many, many industries and jobs transformed or were relegated to much smaller niches.
While it looks like a productivity boost, there's a clear price to pay. The more you use it, the less you learn and the less you are able to assess quality.
Worse, it feels productive. But I'd bet if you watched the clock and tracked progress of a non-trivial project, you'd find what we've always known to be true: there are no shortcuts.
I'm sure it's faster in the short term. Just like copy-paste-from-stack-overflow is. But it is debt. The shit builds and builds. But I think the problem is we're so surrounded by shit we've just normalized it. It is incredible how much bloat and low hanging fruit there is that can be cheaply resolved but there is no will to. And in my experience, it isn't just a lack of will, it is a lack of recognition. If the engineers can't recognize shit, then how do we build anything better? It is literally our job to find problems
All the digital artists I know don't use and want new features in Photophop. And more generally, most non-tech businesses values more stability than having new features.
I don't think organization will be able to do this themselves. Transforming vague ideas into a product requires an intermediary step, a step that is already part of our daily job. I don't see this step going away before a very long time.
Non-tech people have the tools to create website for a long time, though, they still hire people to do this. I'm not talking about complex websites, just static web pages.
There will simply be less jobs that there is today.
Regarding job security, in maybe 10 years (human and companies are slow to adapt), I think this revolution will force us to choose between mostly 2 career paths:
- The product engineer: highly if not completely AI driven. The human supervises it by writing specification and making sure the outcome is correct. A domain expert fluent in AI guidance.
- The tech expert: Maintain and develop systems that can't legally be developed by AI. Will have to stay very sharp and master it's craft. Adopting AI for them won't help in this career path.
If the demand for new products continue to rise, most of us will be in the first category. I think choosing one of these branch early will define whether you will be employed.
That's how I see it. I wish I can stay in the second group.
> - The product engineer: highly if not completely AI driven. The human supervises it by writing specification and making sure the outcome is correct. A domain expert fluent in AI guidance.
If AI continues to improve - what would be the reason a human is needed to verify the correct outcome? If you consider that these things will surpass our ability, then adding a human into the loop would lead to less "correct" outcomes.
> - The tech expert: Maintain and develop systems that can't legally be developed by AI. Will have to stay very sharp and master it's craft. Adopting AI for them won't help in this career path.
This one makes some sense to me but I am not hopeful. Our current suite of models only exist because the creators ignored the law (copyright specifically). I can't imagine they will stop there unless we see significant government intervention.
When the design closely aligns with the real world problem it solves, communication pathways are natural and you don't really have to care much about them.
What matters is the Actor's role and making sure it represent a strong domain concept. The rest follows naturally.
But to be fair, it's never that simple and you always end up with some part of a system that's less "well-designed". In that case,figuring out who talks to who can quickly become a nightmare.
Actors are great on the paper, but to benefit from them, you need great understanding of your domain. I tend to use it later in the development process, on specific part where the domain is rich and understood.
I worked for multiple companies remotely and the thing that worked the best for me was:
- Everyone must be connected to Discord in an audio room.
- Encourage pair programming.
- Record every meeting make them available to everyone.
- Log every decision in a central place, easy to browse and discover.
- Meet regularly (IRL) with you colleagues.
By far the most important point is always being on Discord. You can quicky jump in someone's room and feel very connected to your teammates. Obviously, like in a real office, don't disturb someone if it can be managed asynchronously.
It will for sure! Just today the impact is collosal.
As an example, people used to read technical documentation, now, they ask LLMs. Which replaces a simple static file by 50k matrix multiplication.