(no title)
UltraLutra | 7 months ago
I think the cost is more in thousands to cover inference. And, no, I don’t think it’s been proven out that an engineer is so much more productive to justify thousands of dollars a month cost. The models are great for greenfield projects. But a lot of engineering is iterating and maintaining an existing code base——a code base that the engineer is fluent in. So the time savings is writing code specific enough to implement a new feature vs writing a prompt specific enough that the AI can write code specific enough to implement a new feature. The difference between those two tasks is the time savings.
Say that difference is like 10%. You save 10% of your time by using AI, meaning you have 4 more hours a week than you did before. Are you going to spend 4 more hours writing code? No. Some will be spent in meetings. Some will be spent reading Hacker News. Maybe you’ll get two hours a week of additional coding time. So you’re really only increasing your output by 5%.
The so the employer gets 5% more from you if you have AI. If your salary is 10k per month, they wouldn’t pay more than $500. Per month. And you’re probably costing Anthropic >$10k in inference costs per _week_. The economics just don’t make sense.
You can sub out the numbers here and play around with the scenario. I think the cost of inference needs to drastically fall. And I don’t think that happens soon. What might happen 10 years from now is developers are given a laptop with a built-in GPU for AI inference that does much better code auto-complete using AI. That’s something an employer can pay 3k-5k for _once_ as a hardware investment. But the future of AI coding won’t be agents. It won’t be prompt-engineering. The models aren’t going to get much better. It will be simple and standard and useful but unimpressive. It’s going to feel boring. It’s going to feel boring. When it’s working, when it’s mature, when it becomes economical, it always feels boring. And that’s a good thing.
UltraLutra|7 months ago