New Law

Apr. 20th, 2009 11:03 am
acroyear: (don't go there)
[personal profile] acroyear
Shelby's Law of Framework Foresight: When working with "the customer" to nail down exactly what things will be constant and what things will be variable in order to develop an extensible framework for their application space, the first thing they will ask you to do after the first deployment is change the most critical "constant" upon which everything is fixed.

Corollary 1: no amount of User Acceptance Testing will protect you from that law.

Date: 2009-04-20 05:02 pm (UTC)
From: [identity profile] thelongshot.livejournal.com
Course, that is what a Functional Requirements Document is for to help prevent that sort of thing.

Date: 2009-04-20 05:42 pm (UTC)
From: [identity profile] tchwrtr.livejournal.com
Strange, I thought the FRDs are what helped *cause* this sort of thing.

"Oh, we didn't mean we wanted fuzzy bunnies. We meant to say that we wanted green turtles. Can't you just change the spec?"

And so it is changed, and NO ONE TELLS THE TECHNICAL WRITER. Gr. Like we have hours on end to read/re-read/compare versions of specs.

Date: 2009-04-20 07:18 pm (UTC)
From: [identity profile] thelongshot.livejournal.com
Technical Writer? What's that?

(Unfortunately, very true on this contract...)

Date: 2009-04-21 12:18 am (UTC)
From: [identity profile] tchwrtr.livejournal.com
Some days I get the feeling that if the FDA didn't require us, we would not be here. Or at least in the numbers we have--which isn't enough.

Profile

acroyear: (Default)
Joe's Ancient Jottings

January 2025

S M T W T F S
   1234
56789 1011
12131415161718
19202122232425
262728293031 

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jan. 27th, 2026 06:28 pm
Powered by Dreamwidth Studios