4 ms·
> I suppose I'll just start using definitions instead: e.g., "the list of allowed IPs". That's pretty verbose. How about acceptlist and denylist (or blocklist)
by ardy42 6y ago
> I suppose I'll just start using definitions instead: e.g., "the list of allowed IPs".
That's pretty verbose. How about acceptlist and denylist (or blocklist)?
For "master/slave" maybe "boss/worker" would be a good substitute?
- downerending 6y agoIn principle, sure. In practice, when a junior wonders why they can't find anything useful when they google or grep for "acceptlist", then what?
- ardy42 6y ago> In practice, when a junior wonders why they can't find anything useful when they google or grep for "acceptlist", then what? Lots of words have synonyms, so that's not a real problem. Sooner or later the search results will catch up, and in the mean time it's always an option for a junior developer to ask a question or figure things out themselves by looking at the implementation.
- downerending 6y agoNot sure what to say to that. For normal corporate use, this would be standard Dilbert-esque silliness. In safety-critical situations, it would be madness.