> If something that previously took weeks for a human to design, now takes 10 min, that means a whole week of salary went up in smoke.
To me, this is the depressing sentiment. The idea that, somehow, the goal isn't to produce useful things but to spread work out over a period of time in order to maximize payment.
At a high level,I conceptualize my job as "doing useful things." Whether that's design, writing code, debugging, sysadmin, CI/CD, writing doc, whatever. I just want to be useful. If there's some tool that makes that easier, I am happy about it. I don't think that tool will result in my getting paid less. But if it does, oh well.
>But if it does, oh well.
I'm glad our ancestors didn't take that line of reasoning we'd still be feudal serfs. "The lord has come and taken all our grain again? Oh well, at least I've been useful to him."
If our ancestors worried more about technology obsoleting human labor we'd still be subsistence farmers. Priorizing usefulness is why we're rich today.
Weird way to look at it, from another view we can now print a week salary in 10 minutes. Might devalue the output slightly but we still have the product.
Undoubtedly a fundamental reconsideration of political economy is necessary if we are going to go all in with AI. As of now, this technology will exacerbate the existing 'singularities' and wealth disparity distortions in the socio-economic body. And now, basic fucking income is not the answer. Maybe pitchforks.
the 30min-3h of actual coding time is brought down to 10min, with the reviews, testing, consensus building, tracking, decision making all still taking up most of a week.
If something that previously took weeks for a human to design, now takes 10 min, that means a whole week of salary went up in smoke.
When have we automated enough?