Gotrek wrote:
I suggested this few months back, but at the moment the 'need vs cost in
codetime' wasnt high enough.
In the past I have built two eqpool systems for two different societies.
The latest one:
< ~/code/python/eqpool > wc *.py \
admin/{credits,ctransfer,markparty,mischtml-old,selleq,showeq}.py
85 225 2260 addparty.py
31 64 499 common.py
21 32 348 credits.py
42 128 913 creditscommon.py
253 730 7145 dbaccess.py
30 56 588 history.py
20 29 384 index.py
92 243 2547 mischtml.py
65 198 2175 parties.py
16 17 183 rules.py
49 115 1071 showcredithistory.py
74 194 1928 showeq.py
34 67 728 admin/credits.py
67 213 1950 admin/ctransfer.py
56 178 1754 admin/markparty.py
71 204 2128 admin/mischtml-old.py
115 315 3081 admin/selleq.py
76 194 1948 admin/showeq.py
1197 3202 31630 total
< ~/code/python/eqpool >
Let's do little guessing:
Impleting same using LPC takes 5 times more code lines than using Python.
LPC coder with medium experience can do about 2 fully working
lines in a minute. Hmm, it means 5*1200/2/60 = 50 hours. Before coding
the system needs to be designed; let's allocate another 50 hours for the
design phase -> 100 hours totally (actual testing is done by mortals, so
no need to include testing time).
Also we assume our LPC coder is hard-working, he/she uses 3 hours of his/her
free time every day for this project. In theory we should have fully
working system in a month. (In reality it would probably take 3-6 months
since wizards don't have time to code every day.)
-Thelo