httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Rodent of Unusual Size)
Subject Pasta coding
Date Thu, 10 Apr 1997 11:40:17 GMT
    I'm going cross-eyed tracing the the module coroutine callback
    conditionals for documenting in mod_example (the last bit before
    it's done), and it made me think of this.  I'm passing no judgement
    whatsoever on the conditional code, mind you; it works and is clear,
    though not necessarily immediately.


    #ken    :-)}
        Be sure to visit LaughWEB (

*File Description: All About Pasta Code*

Transcribed from the November-December 1992 issue of the Lawrence
Livermore National Laboratory Software Engineering Newsletter.

The mention of ``a feast of spaghetti code'' [``Computer Collectives,''
CrossTalk, April/May 1992] prompted this response by Raymond J. Rubey
SofTech, Inc., Fairborn, OH.

"Nearly every software professional has heard of the term spaghetti code
as a pejorative description for complicated, difficult-to-understand, and
impossible-to-maintain, software.  However, many people may not know the
other two elements of the complete Pasta Theory of Software.

  Lasagna code is used to describe software that has a simple,
understandable, and layered structure.  Lasagna code, although
structured, is unfortunately monolithic and not easy to modify.  An
attempt to change one layer, while conceptually simple, is often
difficult in actual practice.

  The ideal software structure is one having components that are small
and loosely coupled; this ideal structure is called ravioli code.  In
ravioli code, each of the components, or objects, is a package containing
some meat or other nourishment for the system; any component can be
modified or replaced without significantly affecting other components.

  We need to go beyond the condemnation of spaghetti code and to the
active encouragement of ravioli code."

View raw message