Flutterby™! : requirements in the frequency domain

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

requirements in the frequency domain

2024-04-12 01:24:41.128201+02 by Dan Lyke 0 comments

RT Shae Erisson @shapr@recurse.social</a

OH:

J: Fred Brooks, "The Mythical Man-Month" paraphrased: the engineering manager is a low-pass filter over inputs to the development team.

B: I find very funny the implication that changes in project requirements should be viewed in the frequency domain.

Agile is an attempt to make the resistor in the RC network as small as possible.

[ related topics: broadband Model Building ]

comments in ascending chronological order (reverse):

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.