As for learning dynamic programming in the large, I can't help all that much, because the only large projects (more than a couple of thousand lines) I've worked on have been in static languages (and I spent much of my time fighting the type system. Alas). I suspect that the best thing to do would be to find a large project implemented in a dynamic language (Emacs springs to mind, but Rails/Django/Catalyst would probably be big enough) and have a look at that.
On the other hand, you can do an awful lot in ten lines of (say) Perl, particularly if you take advantage of library modules, CPAN, etc. So even if large-scale programming is easier in static languages, that doesn't mean dynamic languages aren't worth learning :-)
I came across this post (http://www.artima.com/weblogs/viewpost.jsp?thread=217080) while answering your other question - I'm not sure I agree, but it's an interesting way to think about the problem.
no subject
On the other hand, you can do an awful lot in ten lines of (say) Perl, particularly if you take advantage of library modules, CPAN, etc. So even if large-scale programming is easier in static languages, that doesn't mean dynamic languages aren't worth learning :-)
I came across this post (http://www.artima.com/weblogs/viewpost.jsp?thread=217080) while answering your other question - I'm not sure I agree, but it's an interesting way to think about the problem.