Good style in Lojban: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Don't repeat yourself<ref>https://en.wikipedia.org/wiki/Don't_repeat_yourself</ref> | ==Don't repeat yourself== | ||
Every piece of knowledge must have a single, unambiguous, authoritative representation within a discourse<ref>https://en.wikipedia.org/wiki/Don't_repeat_yourself</ref>. Don't copy fragments of your discourse. Instead try to go to higher levels of abstraction to avoid that. Instead of | |||
{{mu|mi do prami .ije do mi prami|I love you, and you love me.}} | {{mu|mi do prami .ije do mi prami|I love you, and you love me.}} | ||
say | say | ||
Revision as of 11:54, 12 July 2014
Don't repeat yourself
Every piece of knowledge must have a single, unambiguous, authoritative representation within a discourse[1]. Don't copy fragments of your discourse. Instead try to go to higher levels of abstraction to avoid that. Instead of
| mi do prami .ije do mi prami I love you, and you love me. |
say
| mi do se xi vei pa je re prami I love you, and vice versa. |
This allows for more tricky examples to be expressed using the same algorithm:
| mi do se xi vei pa jonai re prami Either I love you, or you love me, but not both. |
etc.
Links
- https://en.wikipedia.org/wiki/The_Pragmatic_Programmer
- http://www.grobmeier.de/the-10-rules-of-a-zen-programmer-03022012.html#.U8D4YlWSy2k
- http://blog.codinghorror.com/a-pragmatic-quick-reference/
- http://programmer.97things.oreilly.com/wiki/index.php/97_Things_Every_Programmer_Should_Know