Links

Senior Consultant at Zoomwit Corporation Project Manager at Safe Horizons NA at Personal Sabbatical Project Manager at Bristol-Myers Squibb Senior Programmer / Technical Lead at Bristol Myers Squibb Web Applications Developer / Business Analyst at Bristol Myers Squibb Adult Education Instructor at Murry Bergtraum Adult Education Center Web Developer at New York Universitysee less...

Another great site that aggregates Perl related blogs

This forum is an archive for the mailing list: dbix-class@lists.scsys.co.uk (view options). Messages posted here will be sent to this mailing list.User and developer mailing list for DBIx::Class, an object-relational mapper module written in Perl.

Getting Started with Perl Catalyst Top Ten Resources for New Catalyst DevelopersTen links to get you started using Perl Catalysthttp://dev.catalystframework.org/wiki/http://catalystframework.org/http://search.cpan.org/dist/Catalyst-Manual/http://search.cpan.org/dist/Catalyst-Runtime/http://planet.catalystframework.org/http://jjnapiorkowski.vox.com/http://www.catalyzed.org/http://use.perl.org/http://perlmonks.org/http://www.perl.com/

The following is an edited and updated version of a Moose advocacy bit I wrote on the Google AppEngine for Perl project mailing list quite a while ago. I decided to republish it here since with the recent release of Catalyst 5.8, which uses Moose... Read and post comments | Send to a friend

Following matt’s post about people not blogging enough about Perl, I’ve decided to try to post once a week about Perl. So I will start by a series of articles about what we call modern Perl. For this, I will write a simple feed agregator (using Moose, DBIx::Class, KiokuDB), some tests, and a basic frontend (with Catalyst). This article will be split in four parts:

The elegant MVC framework Catalyst will make web development something you had never expected it to be: Fun, rewarding and quick. New Book! Jonathan Rockway's new Catalyst book, published by Packt Publishing, is now available for purchase. Get it now!

Most shops these days seem to know that using a Version Control System is necessary for the organization of a large software project involving multiple developers.   It’s essential to allow each developer to work on their part of the project and commit the changes to a central repository, which the rest of the developers can then pull down into their working sandbox.  Its an effective way to develop that avoids overwriting of changes, and allows for easy rollback and history.  However, one problem I see over and over again is either lack of branching altogether,  or doing it in a manual way that drifts the branch further out of sync with trunk as time goes on, and then trying to manually merge this with the trunk code when the branch is done.   For those who don’t know, trunk is basically your mainline, in which code can be branched off of for features that won’t interfere with trunk until they are merged at some later point.  This allows for testing changes without bothering other developers, but still being able to keep a commit history.