Pair programming?
oooh, that sounds like fun!

;-)

-Ben

> yeah I think that's it.
> 
> regardless - pretty useful information - awesome actually.
> I am doing some reading at:
> http://www.extremeprogramming.org/
> http://dmoz.org/Computers/Programming/Methodologies/Object-Oriented/Extreme_Prog
> ramming/
> 
> in searching on Extreme Programming I came across
> http://www.pairprogramming.com/
> 
> Great reading. thanks for the direction.
> 
> I have been playing around with some of the concepts without knowing it was 
> "extreme programming" - and I think it lends itself unbelievably well to web 
> application development especially the projects I work on.
> 
> At my last job - I was trying to convince them to create an "innovation 
> centre" - where there were no rules (well theres always rules) - but the 
> emphasis would be on creating applications, experimenting a little bit. Step 
> outside the proverbial box. I was willing to bet that 90% of the innovation 
> would come from just 10% of their IT budget - simply by making the resources 
> available to people who want to contribute, and fostering a collaborative 
> supportive environment for them to create their visions.
> 
> I should note: we outsourced our technical requirements. The company that 
> got the initial contract was a startup - and green in its development 
> methods and structures. We pushed their technical capabilities and had our 
> own challenges and deadlines that weren't being met as a result. What I 
> think we should/could have done is an entirely different discussion... but 
> what we did was get frustrated and squandered the relationship and was 
> forced to find a new technical provider.
> 
> We hired a "structured" project manager to assist the new developers by 
> feeding them detailed specifications. He did a great job - a hardworking 
> detail guy - but I don't think he was really in synch with products and 
> services we were offering and so that created some new problems. Depending 
> on who you talk of course - but yes - you ARE talking ta me right now.
> 
> but I diverge - back to the innovation centre. The innovation centre meant a 
> couple of things to me. 1) it meant I could build web applications - and 
> demonstrate some appoaches to problems in hands on real terms (there's a 
> bunch of stuff I wanted to see happen - and words don't create momentum - 
> XML, LDAP blah balh blah) 2) I wasn't the only one with technical 
> capabilities that had something to contribute. At least 20% of the company 
> had some to excellent technical capabilities - at least 3 of us could have 
> built what we outsourced.
> 
> An example of an innovation centre project. The initial specifications of 
> the site used LDAP for user management and security - good or bad, I don't 
> know, you tell me - but for me it created a bunch of interesting scenarios. 
> The original developers didn't know how to do LDAP stuff so they changed the 
> specification from CF and LDAP to ASP. I liked LDAP because I perceived it 
> as a standard which could be used for authentication for a myriad of 
> potential services built around our core. Web mail, MS Content Management 
> Server (then Resolution) - and whatever. anything that could usse LDAP for 
> user authentication could be quickly added as a service. I wanted to get it 
> to work - to see it work, I do understand that the conception is certainly 
> different that performance - but I really liked the idea of LDAP and wanted 
> to prove/disprove its value.
> 
> I really like the model of XP, and have been thinking about piecing together 
> a collaborative prototype engine that interactively builds a wireframe of a 
> site - and really emphasizes the cooperation and conversation between the 
> different stakeholders on a particular site.
> 
> The model would be something like:
> Step 1. Create a New Concept.
> Step 2. Define Stakeholders
> Step 3. Define Layout of Site
> Step 4. Start Wireframing site - each page has a separate discussion area - 
> each page represents either a piece of content or an application.
> Step 5. Look and Feel
> Step 6. Cycle through content and applications - collecting and building.
> 
> sort of like the wireframing tool thats floating around, combined with the 
> dev notes - with the ability to change layouts, style sheets and graphics 
> etc.
> 
> I'm getting a little out there... time to do some coding.
> 
> Thanks for the link.
> Eric
> 
> 
> 
> 
> From: "Erika L. Walker-Arnold" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: CF-Community <[EMAIL PROTECTED]>
> Subject: RE: tandem development
> Date: Thu, 23 May 2002 19:26:24 +0100
> 
> Extreme Programming
> 
> http://www.google.co.uk/search?q=extreme+programming+book&ie=UTF8&oe=UTF
> 8&hl=en&meta=
> 
> Is this what you're looking for?
> 
> Erika
> With a K
> ------------------------------------------------------------
> 
>  >>| -----Original Message-----
>  >>| From: Eric Dawson [mailto:[EMAIL PROTECTED]]
>  >>| Sent: 23 May 2002 19:12
>  >>| To: CF-Community
>  >>| Subject: tandem development
>  >>|
>  >>|
>  >>| someone posted a link to a book that talked about
>  >>| development practices.
>  >>| This book talked about tandem development teams - ie two disctinct
>  >>| developers working together to finish a single project.
>  >>|
>  >>| Does anyone know what I am talking about or have any
>  >>| insight to this method?
>  >>|
>  >>| Makes total sense to me - and probably creates a great dynamic for
>  >>| outsourced development.
>  >>|
>  >>| Later
>  >>| Eric
>  >>|
>  >>|
>  >>|
> 
> 
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to