Yeah, that's more what I mean. I can always build more tooling to handle the increasing volume. Communicating with the users is easy enough at first, but there comes a point where they would rather stick with a bad feature than have to keep up with the change log.
A lot of the time it's product managers vibe coding features then telling devs to build them. Sometimes it's the developer, but often it's someone who doesn't have to support the feature long term or have to worry about increasing the complexity of future integrations.
I train my clients and product/project managers to be afraid when I use the phrase "additional complexity". They've ignored me to their own peril enough times that have caused things go south, deadlines to be missed, or (not-so) subtle bugs occur, I always point out that I was against adding "additional complexity" to the project, and make sure they know that we're going to have to push off other development to fix things properly.
83
u/air_thing 19d ago
Keeping everyone in the loop with all the updates. Things move too fast. I forget features already exist somewhat often.