A Bunch Of STIFs
Grady Booch states that good software architectures evolve incrementally via a progressive sequence of STable Intermediat Forms (STIFs). At each point of equilibrium, the “released” STIF is exercised by an independent group of external customers and/or internal testers. Defects, unneeded functionality, missing functionality, and unmet “ilities” are ferreted out and corrected early and often.
The alternative to a series of STIFs is the ubiquitous, one-shot, Unstable Fuming Fiasco (UFF):
Note: After I converted this draft post into a publishable one and queued it up, I experienced a sense of deja-vu. As a consequence, I searched back through my draft (91) and published (987) post lists. I found this one. D’oh! and LOL! I’m sure I’ve repeated myself many times during my blogging “career“, but hey, a steady drumbeat is more effective than a single cymbal crash. No?
Leave a Reply
Why am I here?
WTF?
Meh!
D'oh!
My BTC Address
so this is it’s own new and improved cersion, thus illustrating the STIF process, or are you just repeating the same UFF?
It’s whichever you’d like, my delectable Mexican pisces culinary delight. You can call it Revision 1 of the former or rev 0 of the latter. Interpretation is in the fish eye of the beholder?
I see the alternative to a set of STIF’s being a WORM (Will Often Repudiate Management). WORM as the antihihesis of Stiff.
BD00 sez that all parties involved in UFF/UBOMB creation need repudiation. It takes two to tango, no matter who’s the leading stepper.
Like unabashed and biased-BD00 almost always does, it’s easy to trash the guild of infallible management over the workery. But hey, they’re more mature and they get paid more than the porkers in the pen, so they can and should handle it better (in theory). No?