Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

And the issue here is that this future is bringing fundamental change to the nautre of labor without overriding the need for compensation in order to house and feed the populace. Hence the rejection.


I notice your two comments straddle the contradiction "It's definitely not happening, but also it's terrible that it is."


Where was I saying it's not happening?

But if I can clarify my point. It's more that I'm trying to say "Company promises A is happening and B is the necessary consequences to achieve it".

I do not believe A is happening but B is occurring despite that, in order to achieve hidden agenda C. Though in this case, C is not that hidden since every other article has them blabbing out loud about "wow it's going to be so amazing when C happens!"

here,

A = AI is making us more productive than ever

B = This will cause impacts on jobs and the economy as a whole as we realign what labor is

C = Companies make more money than ever as it works towards eliminating labor on massive (90+%) levels in order to maximize profits and moating the idea of knowledge itself


If you think A is not happening for a software engineer's role, then you are mistaken.

We are all scrambling to figure out what else we need to do (and so are many other roles).


> If you think A is not happening for a software engineer's role, then you are mistaken.

En masse, I argue not. More productivity for engineers would not be met with mass layoffs if engineering production was why value was being added. On the contrary, other industries have had to hire back talent becsuse companies were too aggressive cutting people and needed that work to be done.

But I'm not an oracle. I can only speak for what I see today and won't predict tomorrow. Especially in these trying times.


You're reading too widely for a simple point I'm making: what an engineer did in Aug 2025, they can do in a fraction of the time in Aug 2026.

Everything else is something else you care about, but producitivty is simply proven for almost every engineer on the above point.


> You're reading too widely for a simple point I'm making: what an engineer did in Aug 2025, they can do in a fraction of the time in Aug 2026.

You're not getting my point, and it's not hard. I disagree with this statement.

>producitivty is simply proven for almost every engineer on the above point.

I've read otherwise.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: