|
|
|
|
|
by toyg
859 days ago
|
|
Beyond the snark, this is basically it. It's the same reason the Roman Empire, despite all its technological prowess, never tried hard to automate relatively low-hanging-fruit tasks: because slaves were cheap, plentiful, and more flexible ("reprogrammable") than anything mechanical could ever be. If it costs $1m p/y to run a machine that cooks burgers and fries, or $30k for an employee who can do that _and_ cover something else when someone else is ill, it's a no-brainer. But businesses had to discover that the hard way; until the 80s, most people were still convinced automation would win everywhere, because it had won (and won big) in manufacturing. A combination of factors, from the '80s onwards, made labor costs effectively fall, which created our reality where certain jobs are so cheap that automating them makes no sense. The "problem" is that, in certain regions, software development costs reached a point where automation looks very, very appealing. If a machine costs 500k p/y to replace a few 150k p/y SWEs without all those pesky employment complications, businesses will happily choose "AWS AI CloudDeveloper"... |
|
Do you mean an AI programmer would cost $500k per year? If so I think you greatly overestimate the cost.
Recently I did some text processing with GPT-4 turbo (128k context) and I reached the daily limit of 5 million tokens. IIRC it cost me around $70 bucks for the day.
I think $70 is the hourly rate of a SE with $150k salary working 40 hours per week. Note that we are at early stages with this tech, it will probably only get cheaper from here.