Prev: Read CSV in SBCL
Next: New Lisp indenter for Kate
From: Alain Picard on 15 Sep 2009 05:32
sirpi <sirpi314(a)gmail.com> writes:

> On Sep 14, 9:10 am, Alain Picard <Dr.Alain.Picard(a)gmail.com> wrote:
>> sirpi <sirpi314(a)gmail.com> writes:
>> > I was just wondering how many lines of Lisp code you usually  write in
>> > 8 hours.  
>>
>> Anywhere between zero and 500, with 10 being the median.
>>
>> > The purpose is to evaluate the
>> > effort of working as a programmer.
>>
>> For this purpose, the metric is basically useless --- here you
>> want to measure the *quality* of those 10 lines.
>
> Could you give some example, i.e. source code in Lisp, that you
> consider of high quality giving an estimation
> of the time needed to develop that code for a good Lisp programmer?

Well, here's something I wrote a while ago (Gosh - has it been 5 YEARS
already?!) --- a blowfish implementation.

http://members.optusnet.com.au/apicard/blowfish.tar.gz

I guess I'll leave to others to judge the whether it's of "high
quality"; I think it's good enough which gives you an idea of what
I call good. I wrote it to cement my understanding of some basic
crypto techniques and to delve into writing highly optimized numerical
lisp.

The file is 800 lines or so; more than half of which would be
whitespace, comments and numerical constants. Looks like 350
lines of "real code", to me.

I can't remember how long it took me to write, but it was more than
a few spare evenings; let's call it 15 hours of work. So that was
code written at ~ 150 lines per day; definitely on the very high side.

The reasons for this are clear: the requirements are extremely simple,
and well defined, and modular (the code doesn't interact with anything
else). In a "real" project, almost all of the headaches is ensuring
that the code is correct in the context of all the surrounding code
and meshes well with the existing application (e.g. adding a new screen
to an application which has a GUI, for instance), updating the manuals,
updating the automated tests, etc etc.

Other examples would be where I've spent two days finding where to add
the one or two relevant line of code (which would be meaningless here)
but which is unfortunately also a realistic scenario of programming
in the real world at large.

> Perhaps with this example I can get some intuition from an experiment
> Lisper about what is the average *quality*, style, time required and
> so on in a lisp job.

Hope this helps.
From: sirpi on 15 Sep 2009 09:15
On Sep 15, 11:32 am, Alain Picard <Dr.Alain.Pic...(a)gmail.com> wrote:
> > Could you give some example, i.e. source code in Lisp, that you
> Hope this helps.

Thanks.

First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Read CSV in SBCL
Next: New Lisp indenter for Kate