...is right here:
http://jroller.com/page/nweber/20041027#high_level_web_application_frameworks
The fellow expects to be able to do in Rails in a month or two what a
previous team labored over for three years... good times...
Yours,
Tom
Very neat. However, I do want to point out that writing the software is only a minor part of the development process. Deciding what the specifications are is a much larger part (and usually hidden in the coding phase).
-- Matt
It's not what I know that counts, it's what I can remember in time to use.
···
On Fri, 29 Oct 2004, Tom Copeland wrote:
...is right here:
Casinonic Australia – how to get much pleasure?
The fellow expects to be able to do in Rails in a month or two what a
previous team labored over for three years... good times...
Very neat. However, I do want to point out that writing the software is only a minor part of the development process. Deciding what the specifications are is a much larger part (and usually hidden in the coding phase).
The true revelation comes when you realize that writing software is one of the best way to discover requirements. Once you accept that, productivity in software development starts to matter a lot more. You can simply discover requirements faster and try more approaches when creating software is not the final stage of a straight run.
Anyway, I wrote a bit of a response to that original post on:
http://www.loudthinking.com/arc/000335.html
···
--
David Heinemeier Hansson,
http://www.basecamphq.com/ -- Web-based Project Management
http://www.rubyonrails.org/ -- Web-application framework for Ruby
http://macromates.com/ -- TextMate: Code and markup editor (OS X)
http://www.loudthinking.com/ -- Broadcasting Brain