?

Log in

No account? Create an account
chris/CO149
co149
.:::: .. .:.. .:: .:: ::. ::::..:: :..::.

November 2010
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30

Back October 31st, 2005 Forward

vacation! fuck the world!

one advantage of my local coffee shoppe having a liquor license is that I can have a double tall bailey's latte. yummm...

Nearly every software professional has heard 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 conceptually simple, is often very 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 to the active encouragement of ravioli code.

-- Raymond J. Rubey, in a letter to the editor of Crosstalk magazine

Back October 31st, 2005 Forward