maintainability
A function of the user interface - a program that needs to be maintained is something my clients don't want to hear about. Drop it - debug it - bye - bye!

reusability
Probably like you I have so many routines (builders, populaters, etc) that I just paste and edit them for the next project. Some PRGs I just drop in the dev folder and never look at em.

"decomposed"
Are you making fun of me?:-)

"partitioned"
Hmmmm..... sounds divisive

tend to pay a price in overhead (such as calling another routine, parameters, returns values) when compared to those that write in-line code.
My PRGs look like they don't do anything is what I've been told. My procedures are little more than a list of function calls to my procedural framework(s).

Since I am moving to ginko status, I have to use real long function (procedure) names soze I can member what they do.

Speed and style - as long as it don't look or behave like a bench program - I usually feel pretty good (but never satisfied). No seams. No flicker! Smooth and cool!