this post was submitted on 28 Jun 2026
72 points (92.9% liked)
Programming
27489 readers
398 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
I've seen a colleague write an API interface for support technicians with AI. As he adds to it or makes changes, the AI breaks something somewhere else. When you ask how to do something he struggles to find where it is on the interface. He says it should be in the documentation, but he doesn't know where because he vibe coded the documentation as well. Then when he needs to just incorporate extra devices with the same API it becomes a gauntlet because he's not sure what the AI did for the first set and the new set only gets half the functionality. On top of that, we are running days behind schedule because we spend so much time on debugging it.
If this was done properly from the ground up it would be less messy, have more intent, and it could be a framework for other projects.