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?
Date: Wed, 29 Mar 2006 01:09:38 -0800 [thread overview]
Message-ID: <57a21f730603290109u5d84c41flba269d2ef2f4da0f@mail.gmail.com> (raw)
In-Reply-To: <3D71DABB-0EFE-4A27-B6AD-73B59B2BFB80@telus.net>
> 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)
next prev parent reply other threads:[~2006-03-29 9:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:48 erik quanstrom
2006-03-28 14:59 ` Anthony Sorace
2006-03-28 15:23 ` Bruce Ellis
2006-03-28 15:57 ` Gabriel Diaz
2006-03-28 17:29 ` Charles Forsyth
2006-03-28 17:47 ` Gabriel Diaz
2006-03-29 0:27 ` Fernan Bolando
2006-03-29 2:49 ` geoff
2006-03-29 7:29 ` geoff
2006-03-29 2:07 ` Paul Lalonde
2006-03-29 3:17 ` quanstro
2006-03-29 3:56 ` Paul Lalonde
2006-03-29 9:09 ` Taj Khattra [this message]
2006-03-29 16:02 ` uriel
2006-03-29 22:03 ` Taj Khattra
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 1:13 erik quanstrom
2006-03-27 4:30 Fernan Bolando
2006-03-27 6:50 ` geoff
2006-03-27 7:25 ` Steve Simon
2006-03-27 9:18 ` Fernan Bolando
2006-03-27 13:10 ` Lluís Batlle
2006-03-27 17:26 ` Fernan Bolando
2006-03-28 0:38 ` Anthony Sorace
2006-03-28 13:59 ` Eric Grosse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57a21f730603290109u5d84c41flba269d2ef2f4da0f@mail.gmail.com \
--to=taj.khattra@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).