News for hackers. Stuff that matters.
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).
Re:Evolution of a Python programmer by rubinelli on Friday January 29, 2010 @03:11PM (#1087439)
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.
Re:Evolution of a Python programmer by pwhelan on Friday January 29, 2010 @02:25PM (#1087299)
Productivity can only be measured by lines of code-- what a co-worker told me. Reminds me of that dark, evil place.
Re:Evolution of a Python programmer by yan on Friday January 29, 2010 @02:26PM (#1087303)
Likewise, productivity of surgeons can only be measured in numbers of stitches.
Re:Evolution of a Python programmer by drawkbox on Friday January 29, 2010 @02:06PM (#1087246)
Gotta get that LOC count up.