|
|
|
|
|
by arjie
225 days ago
|
|
The slow transformation of 'deprecating' to 'ending' has somehow happened across a period where I didn't notice it happening. Most recently this bit me when a place I was contracting at received notice that a vendor was 'deprecating' some old API they used in May of 2025. Okay, thanks for the warning, and I'll prioritize dealing with that later in the year. As it so happens, the vendor intended to say that they were insta-sunsetting/deleting/ending-access-to that endpoint. The switch wasn't too much effort for an engineer on the team but that was honestly my first encounter with the fact that "deprecation" today means "deletion" to a lot of people. There's a few things like this that have semantic drift over time: 1. deprecate -> delete 2. refactor -> rewrite 3. data normalization -> data cleanup 4. hash/encrypt -> now often interchanged 5. authenticate/authorize -> interchanged 6. bricked -> has error, often recoverable |
|