J/HouseStyle: Difference between revisions
Content added Content deleted
(→{{header|J}}: regarding ledes and code re-use) |
(→suggested format & style: word fiddlying, focus on consistent brevity) |
||
Line 72: | Line 72: | ||
We have several nebulous purposes on this site, but IMO the primary one is advocacy. So here are my thoughts on a '''''style''''': |
We have several nebulous purposes on this site, but IMO the primary one is advocacy. So here are my thoughts on a '''''style''''': |
||
In order that J garner notice and perhaps converts, the J code should differentiate itself. One way to do this is to keep the code short |
In order that J garner notice and perhaps converts, the J code should differentiate itself. One way to do this is to ''consistently'' keep the code short, to pique interest and preclude [http://www.urbandictionary.com/define.php?term=tl%3Bdr TL;DR]. However, the code should not be so dense as to be impenetrable, to preclude [http://rosettacode.org/mw/index.php?title=User_talk:Dkf&diff=63678&oldid=53652 sentiments like these]; at the very least the names should provide some hints. |
||
Another way to do differentiate J is to emphasize its unusual or powerful aspects. This includes: |
|||
:# Preferring tacit code to explicit, |
:# Preferring tacit code to explicit, |
||
:# focusing on function composition and powerful and unusual primitives, such as <code>&.</code> and <code>^:</code>, and |
:# focusing on function composition and powerful and unusual primitives, such as <code>&.</code> and <code>^:</code>, and |