It sounds awfully like a rehash of Fred Brooks' surgical team model.
Well, Surgical Team was a way of organizing a standing team. I was talking about a group of engineers who would roam around the code base working on reducing technical debt; it has nothing to do with how normal project teams are organized.
I remember reading a hacker book in High School (1983) called the Adolesence of P1. anyone else remember this?
Yup. I read it in junior high and thought it was great. I found it in the library in college and reread it--unfortunately in between I had developed some literary sensibilities (not a lot, but a few) and didn't dig it quite as much. But if I could find a copy, I'd grab it and read it again.
I'm not a true lisp hacker but from lurking on comp.lang.lisp I believe that the lisp guys belive that a good Common Lisp implementation can get pretty kickin' numeric performance. Of course you have to put in various declarations to allow the compiler to generate efficient code. But if you do that, it's supposed to be pretty good. And the advantage is you can build up your program without the declarations, get it working and then optimize by adding them in. Or that's the theory. Also these things vary from implementation to implementation--some are more tuned toward numeric style computation than others.
Slashdot Mirror
It sounds awfully like a rehash of Fred Brooks' surgical team model.
Well, Surgical Team was a way of organizing a standing team. I was talking about a group of engineers who would roam around the code base working on reducing technical debt; it has nothing to do with how normal project teams are organized.
> LOL. Where are the Lisp bindings for MySQL?
http://clsql.b9.com
-Peter
Yup. I read it in junior high and thought it was great. I found it in the library in college and reread it--unfortunately in between I had developed some literary sensibilities (not a lot, but a few) and didn't dig it quite as much. But if I could find a copy, I'd grab it and read it again.
I'm not a true lisp hacker but from lurking on comp.lang.lisp I believe that the lisp guys belive that a good Common Lisp implementation can get pretty kickin' numeric performance. Of course you have to put in various declarations to allow the compiler to generate efficient code. But if you do that, it's supposed to be pretty good. And the advantage is you can build up your program without the declarations, get it working and then optimize by adding them in. Or that's the theory. Also these things vary from implementation to implementation--some are more tuned toward numeric style computation than others.