Some people who don't use AI will be left behind - those who work on things where LLM's are capable of a substantial amount of the tasks will be left behind if they just refuse to leverage the superhuman properties that LLMs have.

I don't think it's hard to catch up if such a person changes their mind, though.

Some people who do use AI will be also left behind - those who use it to replace their skills without developing new ones themselves, and those who use it to do the same or worse work more cheaply. They will be left behind in a competitive world where others will work out how use it to do more or better work with no reduction in effort.

▲

fdsajfkldsfklds 10 hours ago | parent | next [-]

>those who work on things where LLM's are capable of a substantial amount of the tasks will be left behind

It sounds more like there is no chance that most of those people will stay employed, regardless of how "ahead" they try to stay.

▲

moron4hire 10 hours ago | parent | prev [-]

If LLMs mean I never have to open a PowerPoint from a client to pull out their "data" again, that'd be great. I gain nothing from being a manual data entry monkey for people who don't understand the concept that presentation-ready output formats are not data transmission formats.

But if I'm to be expected to employ vibecoding in my day to day job as a software engineer, I'll dismantle my house and go live off grid somewhere in Alaska. I have enough power tools and knowledge to do it. Probably massively healthier for my kids.

▲

furyofantares 10 hours ago | parent [-]

For now at least, I think it really depends on what type of coding that is.

I don't have any particular predictions going forward about it, but something I think about right now is, do I want to focus my time where the interesting decisions, the valuable contributions I make, are product-level thinking about what to build and what problems to solve? Or do I want to focus my time where the interesting decisions are technical ones, fully wrapping my head around a technical problem and coming up with a solution?

I do think both options are still available, and personally I love them both. But I don't know what types of coding would involve significant amounts of both activities anymore.

	▲	skydhash 10 hours ago \| parent [-]
		There’s still a lot of place for both. Because they are just a shift of perspective around the same thing: Solving a problem for someone. Product is when you’re seeing things as the one who have the problem and designing the solution in a way that is usable. Technical is when you shift to see how the solution can be implemented and then balancing tradeoffs (mostly costs in time and monetary resources). While the code is valuable (as it is the solution). Building it is quite easy once you have a good knowledge on both side. The issue with AI is not in their capabilities, but in people rushing to accept the first version when there are still unknowns in the project. And then, changes costs almost as much as redoing the project properly.