> If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver bot

> If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver both in terms of communication and mental effort. For internal processes, this is fair enough. But anything that will be exposed to an end-user should be simple without shorthand.