SOFTWARE: Refactoring vs Maxfactoring

Posted on June 10, 2006. Filed under: Visual FoxPro |

noun, verb
1. the process of gradually improving the ‘look and feel’ of a software application in small chunks
2. partaking in the UX initiative of ‘results driven application surface design’
The result is aesthetic only, there is no change in functionality, performance, stability, scalability or reliability. Side effects include improved sales and perceived higher quality.
Usage (n): ‘The software team spent 3 weeks on the maxfactoring…’
Usage (v): ‘I spent some time maxfactoring my application today…’
an application can be described as having been ‘maxfactored’ once its visual appearance has been improved (ie the ‘user story’ has been enhanced)
Maxfactoring is a low cost, high benefit activity for software companies to apply, along with code refactoring, to software that is approaching functional completeness
(With apologies to a well known cosmetic company)
[See also Perception is everything]

Make a Comment

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

One Response to “SOFTWARE: Refactoring vs Maxfactoring”

RSS Feed for Craig Bailey on Microsoft Comments RSS Feed

Interesting concept…so now we need a MaxFactor (boy, the lawyers are just getting itchy right now!) Wizard to go through an existing application and clean it up.

Where's The Comment Form?

Liked it here?
Why not try sites on the blogroll...

%d bloggers like this: