3 ms·
Can you help me understand the costs? Because as far as I can tell it is: 1) "We should consider using Allowlist" "ok, but let's be careful with externally fac
by carbadtraingood 4y ago
Can you help me understand the costs? Because as far as I can tell it is:
1) "We should consider using Allowlist" "ok, but let's be careful with externally facing APIs, in exactly the same way we change all our externally facing APIs?" "Sure!"
2) "I was editing this file, find/replaced a couple cases of whitelist while I was in there" "LGTM"
3) "Oh, hey, noticed we had nearly finished opportunistically replacing whitelist. Does anyone mind if I just finish up?" "Sure, timebox it?"
Like, it's extremely low cost? What costs are you imagining?
- mariusor 4y agoI'd like to add a point that I haven't seen discussed regarding the cost of change. In many languages a lot of computer related terms have no native correspondent, therefore they use the ones borrowed from English. If the English IT community decides en-masse to change those terms, the best result is that these people will have to catch up - with some unknown delay - or that they'll not bother, and there will be a disconnect in the terms. Which one is more likely and what the overall effects will be, I have no idea. But it will be a point of friction.