From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <57a21f730603290109u5d84c41flba269d2ef2f4da0f@mail.gmail.com>
Date: Wed, 29 Mar 2006 01:09:38 -0800
From: "Taj Khattra" <taj.khattra@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gnupg or pgp for plan9?
In-Reply-To: <3D71DABB-0EFE-4A27-B6AD-73B59B2BFB80@telus.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <facca0919a3c871e40ec39b28adccfa8@terzarima.net>
	<3D71DABB-0EFE-4A27-B6AD-73B59B2BFB80@telus.net>
Topicbox-Message-UUID: 24c1abda-ead1-11e9-9d60-3106f5b1d025

> It happens because engineers are too lazy or scared to try to
> understand the code they are modifying, and a layer seems safer.  My
> case was 3 years of 2 code teams.  Imagine 10 years of open-source-
> like distributed development :-(

your experience tallies with slide 24 from jerome saltzer's "coping
with complexity":

    Why aren't abstraction, modularity, hierarchy, and layers enough?
    - First, you must understand what you are doing.
    - It is easy to create abstractions; it is hard to discover the
*right* abstraction.
    - It is hard to change the abstractions later.
    (ditto for modularity, hierarchy, and layers)