Hi John,
IMHO, with medium sized projects which are not application software to
be installed on a greater number of unknown systems, the problem
described by you is less aggravating:
Hackage offers a fairly good track of version history and I for myself
have adapted versions a good deal of times and found it - easy, to be
honest.
Speaking about small and especially medium sized projects, I think agile
development fits well this scope. Please do not forget this.
Nick
John A. De Goes wrote:
On Oct 1, 2009, at 12:13 AM, Curt Sampson wrote:
And as far as something like dealing with a changing language and
libraries, the mainstream already has well-established and popular
techniques for doing just: agile development.
A project manager's worst nightmare:
"Sorry boss, but we're just not going to be able to meet that
deadline, because, well, a language extension we were using was
dropped from the language, and the syntax for some core operators was
changed. Not only is our code broken, but many of the libraries we
were using are broken. Don't worry, though, we're 'agile', so our unit
tests will tell us when our code is working again."
Big business demands stability.
Regards,
John
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
