My last job, I was the IT manager for a rapid-development environment.   50 or 
so programmers.  These guys programmed by the skin of their teeth.  No long 
development meetings, no BS, just here's what we need , do it.

The software wasn't for commercial use, so they could tolerate bugs and fixed 
them on-the-fly, but there was a huge amount of code being written without the 
endless meetings and design documents.

And the stuff worked.



--- On Thu, 11/20/08, Paul McNett <[EMAIL PROTECTED]> wrote:

> From: Paul McNett <[EMAIL PROTECTED]>
> Subject: Re: [NF] Lean or Agile which do you prefer?
> To: [email protected]
> Date: Thursday, November 20, 2008, 7:15 PM
> Ted Roche wrote:
> > 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 agree! It's just that when looking at something like
> what Stephen posted, my eyes 
> gloss over and I think "endless meetings".
> 
> 
> > 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.
> 
> I'm bringing in more automated testing, including
> continuous integration testing 
> triggered by Subversion commits for 2 target platforms, but
> given that I'm only one 
> guy and can't be down for weeks getting things like
> this set up, it is happening 
> iteratively over time.
> 
> The great thing is that with every new thing I bring in,
> the more knowledgeable I am 
> in total, whereas in a big company there'd be the
> continuous-integration-guy, and 
> nobody else would know how to set it up.
> 
> I do wish I could fork multiple processes of myself.
> 
> Paul
> 
> 
> _______________________________________________
> 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.


_______________________________________________
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.

Reply via email to