Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Would you extend this to all names and not just product? I attempt to push domain driven design and one of the principles is that a single concept should be called by a single name. It all works well until product management decides to unilaterally push renaming of of concept in UI for vague 'market' reasons...


I do. In my current project there is a rule: if marketing touches it, it's not a name, it's a label.

Starting from the code repository and down to the variables names, only technical identifiers are treated as stable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: