Chunking up your code -- subroutines, modules, or best, objects -- let you encapsulate behavior. Instead of building a 3000 line monster, you build a toolkit of little safe, snap-in software components, then build these up into larger components.

Takes some investment to learn this style of coding, but Very Much Worth it. See for example, perlboot, or Damian's book.

When writing code this way, I often feel I am getting nothing done -- just building (and unit testing!) little safe easy functions.

I work and work and work, and nothing seems to be happening (except happy tests), then all of sudden the larger app stands up walks.

It is almost suprising to see it.

And it feels good to know you don't remember anymore how every tiny detail in the system works, but that is OK, you're safe,

• because you have your tests and
• because you've encapsulated and
• because you have well-defined APIs and
• because you have good variable names and method names, ala the refactoring folks.

Just my two cents.

rkg