When I’m learning some new thing, if I’m lucky, there’s a bunch of documentation, tutorials, and examples I can use to get started. Once I’m marginally proficient, I like to go back and revisit those items for a variety of reasons. For example:
- I now have some context for ideas that weren’t clear before, and they make more sense.
- I can understand why the author made some of the choices they did when selecting what to say (or not say) on a particular subject.
- I have more ability to fiddle with the examples, and try some of the things I may have learned.
Generally, going back through some of the basics let’s me “fill in” some of the stuff I may have missed the first time around or “unlearn” some bad habits I may be acquiring. It also helps give me a more solid foundation and more complete understanding to build on.
So, I’m going back through the Catalyst Tutorial. Apparently, in the time between when I first went through it and today, elements of the tutorial have been updated (yay!) and I need to update a zillion components of Catalyst, DBIx, SQLite, etc. (boo!)
So far this evening, I’ve spent more time running CPAN than flipping through the tutorial.
I respect the fact that the Tutorial has been kept up-to-date. That’s really great. I get the point that “current” is a moving target, especially for projects (like Catalyst) that are composed of many moving parts. I just find it a bit daunting that every time I turn around, I need to stop what I’m doing and run CPAN to get the “latest and greatest” version(s) of whatever. I’m halfway to simply putting the damned thing in cron.
Ah! CPAN is done. Again. Back to the other window…
More as it happens.