Exactly, one of the coding style guidelines.
Another one being KISS: keep it simple, stupid!
I consider these two generally recommendable.
I also read about someone saying in a job interview
he doesn’t write code “larger than me head”.
(It’s been written “me”, reflecting his pronunciation)
Interviewer: “So you don’t write functions so
complicated you don’t understand them.”
Candidate: “No, literally: if it’s size is
larger than me head, it’s too long.”
Something like that. This is a way of KISS.
But the way the interviewer understood it
would have been a better way to do KISS imo.
I also consider RERO and FEFO good practices,
but as with most of the other ones out there,
it’s personal taste which ones one wants to adhere to.
(Release Early Release Often/Fail Early Fail Often)
(FEFO: an Erlang coder’s mantra)
… and then there’s dogfood:
“Eating one’s own dogfood” means using the software
one develops regularly oneself. Not always applicable,
but it usually makes a huge difference both in quality
and usability where employed.
Am 07.07.21 um 17:48 schrieb Thomas Bulka:
Am Mi., 7. Juli 2021 um 17:45 Uhr schrieb 'Mike Day' via Programming
<[email protected]>:
Sorry, Hauke, what’s the DRY principle?
Mike
Hi Mike,
I think it means "don't repeat yourself".
Regards,
Thomas
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
----------------------
mail written using NEO
neo-layout.org
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
