On Thu, Nov 20, 2008 at 12:20 PM, Paul McNett <[EMAIL PROTECTED]> wrote:
> I resist highly-defined development processes. If the definition means that it's fixed and static and therefore brittle and restrictive, I agree. If it's a collection of best practices, the kind of stuff we're already doing, only better and more automated: self-unit-testing, TDD, BDD, small, quick rapid iterations with lots of client involvement, continuous integration testing, well-integrated source code control, well, those can be really empowering to cowboy developers to do the work they love to do. I'm back from a couple days at a Ruby conference, and I'm really impressed with the way that many of the top dev groups have integrated those kinds of technology into their work, and how psyched they are with how it works and the results they get. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
