|
|
|
|
|
by madeofpalk
1528 days ago
|
|
The intention of the feature is that it will have an impact - that's usually the main goal of features. Just because something has an impact doesn't mean it is enforcement. Trust me when I say Google isn't going to throw you in the gulag for putting a word in whatever design doc you're writing. |
|
Enforcements, mandates, suggestions, impacts, governances, features - spitting hairs semantically on the overall issue that tech "features" shape areas that tech and its product owners have no business shaping/influencing/impacting/enforcing but still do anyway, let alone even understand, and the downstream ramifications are significant.
They get away with it partially via enablers like your view which minimize the dynamic to local examples that open up framing the counterpoint as something absurd - yes, Google's gulags aren't built yet.
Edit - to put at least one impact of tech like this another way, it's not Google that puts a user in a gulag. It's the coworker of the user who notices a phrase the coworker also typed, was caught by Google, and the coworker corrected - why didn't that user also change it? All these second order effects were doubtlessly considered by that Google product team, I'm sure? Putting aside my original point that Google doesn't even belong in this space by a mile.