Path: utzoo!yunexus!davecb
From: davecb@yunexus.UUCP (David Collier-Brown)
Newsgroups: comp.arch
Subject: Re: Bloat costs
Message-ID: <11384@yunexus.UUCP>
Date: 31 May 90 11:45:46 GMT
Article-I.D.: yunexus.11384
References: <2793@crash.cts.com> <265D2FE5.2513@tct.uucp> <640@sibyl.eleceng.ua.OZ> <2662CE6C.3E68@tct.uucp> <26798@eerie.acsu.Buffalo.EDU>
Organization: York U. Computing Services
Lines: 31



>chip@tct.uucp (Chip Salzenberg) writes:
[or possibly ``According to ian@sibyl.OZ (Ian Dall)'': the origin is unclear]
>|However, I consider program size vs. programmer time to be a
>|false dichotomy.  I would argue that, once gained, the skill of
>|writing programs that begin and stay small makes a programmer
>|more productive and valuable.  It's a part of the overall
>|"think small, do one thing at a time" mentality that produced
>|Software Tools, Research Unix and Plan Nine.  (But not System V
>|or BSD, unfortunately.)

   In a previous life, I worked for a company that had to get
a 5-subsystem large program package to market in 8 months or less.
The approach was really simple:

	First you make it right,
	Then you make it fast, 
	Then you make it small.[1]

  This spawned ``let's get smaaaaaaalllllll'' as an
invitation to drinks and dinner (:-))

--dave
[1] Attributed to Dick McMurray & Ashok Patel.

-- 
David Collier-Brown,  | davecb@Nexus.YorkU.CA, ...!yunexus!davecb or
72 Abitibi Ave.,      | {toronto area...}lethe!dave 
Willowdale, Ontario,  | "And the next 8 man-months came up like
CANADA. 416-223-8968  |   thunder across the bay" --david kipling