Re:Evolution of a Python programmer
by cabalamat on Friday January 29, 2010 @01:32PM
(#1087135)
The enterprise programmer one is pretty good too. Reminds me of EJB (shudder).
[ Parent
| on HN ]
I don't know, it doesn't look flexible enough. The classes should be wired up at runtime using an XML config file.
I also think it could also split the problem using a pool of threads to achieve better performance. Even better, you could queue up all the factors in a master node and have N slaves pulling from it and multiplying. After the queue is empty, all the master has to do is query each slave and multiply the intermediate results together.
Productivity can only be measured by lines of code-- what a co-worker told me. Reminds me of that dark, evil place.
Likewise, productivity of surgeons can only be measured in numbers of stitches.