Lisp job available in Sydney, Australia
in [Lisp]
|
Prev: Read CSV in SBCL
Next: New Lisp indenter for Kate
From: Pascal J. Bourguignon on 13 Sep 2009 16:55 sirpi <sirpi314(a)gmail.com> writes: > I was just wondering how many lines of Lisp code you usually write in > 8 hours. The purpose is to evaluate the > effort of working as a programmer. The statistics seem to indicate that programmers do on average produce about ten (10) lines of debugged, documented, deliverd source code lines per day, whatever the programming language. cf. for example table 3 in: http://digital.mit.edu/research/papers/178_Cusumano_Intl_%20Comp.pdf Hence the importance of selecting a highly expressive programming language. -- __Pascal Bourguignon__
From: Alain Picard on 14 Sep 2009 03:10 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.
From: sirpi on 14 Sep 2009 06:20 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? For example, in this way: First, the task was ... I analyzed the requirement and specifications in ... time I code a prototype .... (time you spend on it) I tested it (or you can first construct the test system first in order to guarantee the code satisfies the specifications 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. I
From: Espen Vestre on 14 Sep 2009 06:26 Alain Picard <Dr.Alain.Picard(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. I take it as a sign that I've been extremely productive if my code has *shrunk* by 100 lines or more during a day :-) -- (espen)
From: Slobodan Blazeski on 14 Sep 2009 09:56
On Sep 14, 12:26 pm, Espen Vestre <es...(a)vestre.net> wrote: > Alain Picard <Dr.Alain.Pic...(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. > > I take it as a sign that I've been extremely productive if my code has > *shrunk* by 100 lines or more during a day :-) If you have problem with over sized code just send it to me , its my specialty :) . Personal record five screens into 5 lines. Bobi http://www.linkedin.com/in/slobodanblazeski |