The descriptor should either be unqualified "Purchases", not "Your/My Purchase", which is redundant and pandering, or, for any feature which can scale beyond a single user, identify the relevant user (your enterprise customers will thank you): "username => Settings". It's also useful to classify groupings, tags, or other attributes (Engineering, Accounting, HR, etc.) and integrate these with security and other aspects.
I always found "My Computer" to be annoying. It's pedantic (no shit, this is my computer), or wrong (no, this is Mike's computer, I'm just borrowing it), or void of useful context (this is a multi-user computer but I'm accessing it from my or someone else's account).
From a testing perspective, individually naming elements based on their ownership attribute makes for hell in scripting, testing, or writing suitable generic instructions (how do you tell Aunt Tilly how to change her settings when "My Computer" has been sensibly renamed "Aunt Tilly's Computer"?).
Sub-par article fails to consider many other relevant alternatives and considerations.
I always found "My Computer" to be annoying. It's pedantic (no shit, this is my computer), or wrong (no, this is Mike's computer, I'm just borrowing it), or void of useful context (this is a multi-user computer but I'm accessing it from my or someone else's account).
From a testing perspective, individually naming elements based on their ownership attribute makes for hell in scripting, testing, or writing suitable generic instructions (how do you tell Aunt Tilly how to change her settings when "My Computer" has been sensibly renamed "Aunt Tilly's Computer"?).
Sub-par article fails to consider many other relevant alternatives and considerations.