Razzak, although I am tired as hell, due to volunteer work at my alma mater's conference track meet today, namely raking the long jump pit for womens' & men's prelim's and finals, and I hope never to have to work so hard again on a volunteer basis, I had to ask a Q as a result of this message.
That y'all are able to implement on such a short cycle-time, what must have been a request at last week's conference, potentially implies one or more things to me. Now, on the worst-case scenario end of plausible implications is that you're full of bull and simply lying, which I have no reason to believe. At the best-case scenario end is that y'all not only can code, but the implication that you've architected the system and its code well enough that your developers know the structure of the system and well enough that most mod's can be made w/o changes in the architecture of the system. Okay, I hope that you'd be the first to candidly admit that y'all ain't perfect. Nevertheless, if I may assume that it's stable/bug-free, at least in integration tesing, to have implemented functionality that you apparently had not included in your original functional spec's on such a short cycle time implies to me that you're doing something very correctly in your approach to managing the system design/architecture as well as its implementation/code. Okay, while I won't say anything more now about good architecture facilitating good change management, etc, etc, etc, I'll offer a parable I've come up with that I very much like. Let's suppose you manage a fleet of piston-powered, propeller-driven aircraft. Let's say you don't do a good job of maintaining logs f/op's like flight, maintenance, engineering (change notices), etc, and that there is no FAA or other governing body to force you to do so. Now, let's say it's circa 1960 and Boeing has just demonstrated the 707. Well, now you want the new technology, jets, turbines, swept wings, and all that jazz. But let's say you still don't do a good job of management. The only difference the new technology is gonna' make is that, assuming it hasn't happened already, when that new technology hits the ground, it'll be moving about twice as fast as that old technology. The moral is, more or less, doing the wrong thing faster makes no difference. The difference ain't simply the technology, it's how well you manage whatever technology you got that's far more critical to success. (I've probably angered any WWW maniacs who totally missed the dot-com bubble bursting, but I think this is a good way to explain things.) F/y'all at RBTI, it ain't just a re-write of RB in Delphi, but what I hope is a better job of architecting and implementing the system. I will also re-iterate my rec' to get and read a copy of "High Stakes, No Prisoners", by Charles Ferguson. As the manager of a S/W company, this read should be worth a lot to you. Keep it goin, I remain hopeful, but managerially rational, meaning I want to see v7 and what it'll do. Later, Steve in Memphis > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of A. Razzak Memon > Sent: Friday, April 26, 2002 3:22 PM > To: [EMAIL PROTECTED] > Subject: The Magical R:BASE 7.0 - Running EEPs in DBGrid > > > > > To All Conference Attendees and R:BASE 7.0 Beta Testers: > > > I'm very pleased to inform you that our Dream Team has > implemented the functionality of running EEPs in DBGrid. > > The DBGrid Object Inspector will include the options for: > > . On DBGrid Enter > . On Column Enter > . On Column Exit > . On Column Moved > . On DBGrid Exit > > > Ms. Karen Tellef, this one is for you! > > Stay tuned for more ... > > Very Best Regards, > > Razzak. > > P.S. Yes, I'm having fun! > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
