Home > Archive > PERL Beginners > October 2005 > Project planning
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Steve Bertrand 2005-10-20, 9:55 pm |
| Hi everyone,
This question may seem odd, but here goes anyway.
I've been working at an ISP for a few years now, and have been adding
to/modifying their current accounting system since I've got here. Of
course it is all Perl based.
This isn't a technical problem I'm having, but the system has well over
100,000 lines of code in several files. I want to change course, and
take a more organized approach to this.
My question is if there are any good books (particular to Perl), on how
to organize a large project like this to make it easier to consolodate
code, find code, and otherwise prevent myself from continuously
re-inventing the wheel. I am quite familiar with Packages, but I just
need some guidance with documenting/planning of the project.
Any tips very much welcome.
Tks,
Steve
| |
| Wiggins d'Anconia 2005-10-20, 9:55 pm |
| Steve Bertrand wrote:
> Hi everyone,
>
> This question may seem odd, but here goes anyway.
>
> I've been working at an ISP for a few years now, and have been adding
> to/modifying their current accounting system since I've got here. Of
> course it is all Perl based.
>
> This isn't a technical problem I'm having, but the system has well over
> 100,000 lines of code in several files. I want to change course, and
> take a more organized approach to this.
>
> My question is if there are any good books (particular to Perl), on how
> to organize a large project like this to make it easier to consolodate
> code, find code, and otherwise prevent myself from continuously
> re-inventing the wheel. I am quite familiar with Packages, but I just
> need some guidance with documenting/planning of the project.
>
> Any tips very much welcome.
>
> Tks,
>
> Steve
>
>
I am sure there are plenty of others, 3 I would suggest,
- Learning Perl Objects, References, and Modules
- Object Oriented Perl
- The Pragmatic Programmer
Sounds like the system has grown enough that it should be broken into
objects to prevent duplication, among all of the other things OOP
provides. The first two above should give you the tools to accomplish
the suggestions about general programming that the third provides.
Good luck,
http://danconia.org
| |
| Peter Scott 2005-10-21, 7:55 am |
| On Thu, 20 Oct 2005 11:59:08 -0400, Steve Bertrand wrote:
> I've been working at an ISP for a few years now, and have been adding
> to/modifying their current accounting system since I've got here. Of
> course it is all Perl based.
>
> This isn't a technical problem I'm having, but the system has well over
> 100,000 lines of code in several files. I want to change course, and
> take a more organized approach to this.
>
> My question is if there are any good books (particular to Perl), on how
> to organize a large project like this to make it easier to consolodate
> code, find code, and otherwise prevent myself from continuously
> re-inventing the wheel. I am quite familiar with Packages, but I just
> need some guidance with documenting/planning of the project.
My book "Perl Medic" is designed to help people in situations like this.
--
Peter Scott
http://www.perlmedic.com/
http://www.perldebugged.com/
| |
| Alfred Vahau 2005-10-22, 6:55 pm |
| Hi,
The newly released book "Perl Best Practices" by Dr. Damien Conway may
be helpful in addition to those recommended already.
Alfred,
Steve Bertrand wrote:
>Hi everyone,
>
>This question may seem odd, but here goes anyway.
>
>I've been working at an ISP for a few years now, and have been adding
>to/modifying their current accounting system since I've got here. Of
>course it is all Perl based.
>
>This isn't a technical problem I'm having, but the system has well over
>100,000 lines of code in several files. I want to change course, and
>take a more organized approach to this.
>
>My question is if there are any good books (particular to Perl), on how
>to organize a large project like this to make it easier to consolodate
>code, find code, and otherwise prevent myself from continuously
>re-inventing the wheel. I am quite familiar with Packages, but I just
>need some guidance with documenting/planning of the project.
>
>Any tips very much welcome.
>
>Tks,
>
>Steve
>
>
>
>
|
|
|
|
|