From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gnupg or pgp for plan9?
Date: Tue, 28 Mar 2006 19:56:37 -0800 [thread overview]
Message-ID: <5A61E36C-CDCF-4198-BE95-22EF3F66B79C@telus.net> (raw)
In-Reply-To: <699553fd641e4d70ce360ad04b2f8ff6@quanstro.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I should have said "time-pressured" not lazy; but yes, bang on.
Paul
On 28-Mar-06, at 7:17 PM, quanstro@quanstro.net wrote:
> i don't personally know any lazy engineers, but i do know quite a
> few that are scared of
> being the scapegoat.
>
> i worked on a big full-text search project that never wrote its own
> search engine. we used OpenText pat, pls/cpl (later bought by
> aol), excalibur,
> inktomi hosted search and probablly a few that have been
> forgotten. these interfaces
> were very difficult to write because what we needed from a full-
> text search engine
> was never what was provided, they all had major bugs and performace
> was generally very
> poor.
>
> yet -- though i'm convinced it would have been easier, and the
> results better --
> nobody had the guts to write an engine.
>
> - erik
>
> On Tue Mar 28 20:08:59 CST 2006, plalonde@telus.net wrote:
>>
>> 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 :-(
>>
>> Paul
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEKgV1pJeHo/Fbu1wRApWpAJ4hjUmIA+eZAdnq9cg11N0whyAS7ACgilM4
zmNi36AKWK0PjX6Xp+t2TuI=
=QSbC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-03-29 3:56 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 [this message]
2006-03-29 9:09 ` Taj Khattra
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=5A61E36C-CDCF-4198-BE95-22EF3F66B79C@telus.net \
--to=plalonde@telus.net \
--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).