I've always liked the "If it's a routine that takes up
more than a page, break it into subroutines"
Though I really follow
Redundent areas get put into subroutines
Use descriptive names for your subroutines so that it should
be intuitive what they are doing. Comments can help as well
Update:
Coding style links, not just sub issues:
Regarding style
Suggestions for working with poor code
Silly code reviews and shift
A few style suggestions The thread's good, but I like tilly's points
is this correct? Some subroutine pitfalls illustrated
Call Subroutines by Approximate Name No help, but amusing
Monk ethics: Beauty vs. Power
A question of style
Another commenting question, More on commenting
p.s. Nothing like archaeological digs through the monastery.
Tends to be a good learning experience.