this post was submitted on 30 Jun 2026
38 points (95.2% liked)
Programming
27564 readers
258 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Assuming a dev company, first thing I would do is let the manegement know, in writing, that building a dependance on AI into your processes will make you depend on a tool that is currently heavily under-priced, with operating costs for all AI firms resulting in hundreds of millions of losses, that they will want to recuperate eventually.
Link articles about firms blowing the yearly budget on per-token price in a single month. Companies spending 500mil per month on tokens woth uncapped usage.
Also explain that allowing your devs to use it will lead to erpsion of their skill, building a dependency, that will then tie their productivity going forward to the whims of AI companies, that are currently operating at heavy losses.
Link any of the numerous papers how AI erodes skill of devs.
Ask them if they really want to build a dependency into this ecosystem, and if they are willing to pay the heavily increased price, once it inevitably gets expensive. That you can start replacing devs with AI, but even now, at the heavily undercut prices, it's already costing more than a developer would, and it will only get worse. There are articles for that too. Make sure to highlight that you will be giving control of your systems and development to something that will be expensive, and it will be expensive to walk back on those decisions, once it's integrated deep enough.
Get a paper trail. Make them sign off on the risks. Don't do anything unless they sign off on the risks, and make it super clear how stupid idea it is. Bring as many recipes, papers, and blogs you can find.
Make a citation for how much it would cost to run a competitive local models. How much you would have to spend on GPUs to have a local solution for all of your planned AI need, so you can continue working once third party AI is not affordable.
Also take a look at all currently unresolved GDPR and general laws around copyright, unsolved cases. Send them blog posts that imply that there might be a copyright problem with AI generated outputs down the line, once all lawsuits resolve.
Mention the google lawsuit in germany, where Google might be legally responsible for the outputs it's AI gives. Ask if that is a risk they accept, assuming it passes.
It's an extremely stupid idea to currently even consider being dependant on AI. Give the recipes and arguments, and have them directly sign off on every risk you can think off. Basically - whatever you do, do a proper long term risk analysis, and make sure the management signs off on the risks.
You will need it down the line. There is a lot of risks.