3 ms·
What's in a Name?
- KingOfCoders 3y agoThe problem with a name is often it reflects what the code does [0], then people add to the code. Then the name gets longer and longer when it should reflect what it does. Start with a name that is abstract enough so it's resilient to changes in it's implementation. [0] e.g. Login() then LoginSso() then LoginSsoOnlyGoogle() etc.