Yes, and if its more than some weeks of hacking it will never work until
it's well written and documented. /Erling
On 2014-07-15 17:19, robert therriault wrote:
Hi Erling,
I agree with your assessment for what I think of as production code that will
be used by third party users. In the case of Raul's reference, I think of it
more as proof of concept coding. The goal in this case is to create a work that
can act as a prototype. If it is useful, then steps must be taken to clean it
up and make it maintainable (but first it needs to work). I see that as one of
the big differences in the ways that I code, which is more of a bricolage
approach, and the coding of programmers who create production code.
Cheers, bob
On Jul 15, 2014, at 8:10 AM, Erling Hellenäs <[email protected]> wrote:
Programs tend to have users? When the programmer is finished he leaves? After a
while someone is supposed to maintain 5 millions lines of code? Fix bugs and
make needed changes? Wake up, if you write a decent program it's used for ages,
and you're not there to explain it. It must be documented? The code must be
self-explanatory? /Erling
On 2014-07-15 16:58, Raul Miller wrote:
Here's an excellent writeup that I think is relevant in the context of
readability:
http://prog21.dadgum.com/87.html
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
