Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

gnat (29)

gnat
  (email not shown publicly)

Journal of gnat (29)

Wednesday March 26, 2003
09:08 AM

Design decisions

[ #11245 ]
Very interesting writing from Mitch Kapor: Making Design Decisions: Some Principles.

1. Implementation must be sequenced

It's not a real project until commitments are made to defer some capabilities. Doing everything at once is not an option.

--Nat

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Doing everything at once is not an option.

    Would you please, please, please call my boss and tell him this? We're working on an inventory system and we all know how ridiculously easy those are to write, yes? The owner said (and he was dead serious) that he wanted it done in two weeks. Now, two months later, we've been given another month extension. Meanwhile, I've been pulled off of that project to work on another, but there's no word of leeway in the deadline.