|
|
|
|
|
|
by serial_dev
54 days ago
|
|
|
> Was there really no internal discussion from a code review at least? This seems hard for me to believe. The outlined story feels unfortunately very believable to me. Teams need to push out the most number of features, and nobody stops even for a second to think about how a feature might affect other flows or other users not in the feature request. It might have been quickly reviewed to check if the code does what it needs to do (add the coauthor note). Do you think reviewers will think about unwanted effects, when they need get back to feeding their own poorly thought out and underspec’d features to their LLMs? |
|
|
>The outlined story feels unfortunately very believable to me.
100% agree here - we seem to forget that most developers hate code reviews. I actually laughed out loud at the use of the word "discussion," it's so rare people want to get together and talk about changes. By the time the PR is up anything that stands in the way of merging and shipping is seen as a nuisance.
To my mind this whole debacle is not really the individuals fault or even the team's fault but the economic pressures that drive people into situations like this.