Comments on: Development practices

By: Liste non exhaustive des thématiques abordées lors des THATCamp | ThatCamp Paris 2010

Tue, 04 May 2010 07:52:40 +0000

[…] thatcamp.org/2008/05/development-practices/ […]

By: Dave Lester

Dave Lester — Fri, 30 May 2008 14:09:59 +0000

To add to this, maybe this session could touch on bridging communication between developers and project managers/non-technical staff. Without getting knee-deep in code, what are ways that code benchmarks and progress can be shared? Trac can be confusing/intimidating to people who don’t use it on a daily basis.

In addition to Trac and SVN, we’ve used Basecamp as a way to communicate internally while using mediawiki for public documentation. Together, how can we make these ‘play nice’?

By: Tom Scheinfeldt

Tom Scheinfeldt — Fri, 30 May 2008 13:36:42 +0000

Travis–

This sounds like a great session, separate from sustainability and project/institutional management discussions. We have been struggling with these issues at CHNM for years. I think the lesson we’ve learned from all this struggle is that development practice is something of a continuous experiment, demanding constant tinkering as technologies, project requirements, personalities, and times change. Yet that doesn’t mean there aren’t good and bad practices, and I’d be very interested to hear about others’ experiences.

Thanks!

Tom

By: James Smith

James Smith — Fri, 30 May 2008 13:35:36 +0000

My development environment (I’m a team of one) is subversion for source management, trac for repository browsing, feature tracking, mediawiki for general web documentation, and wordpress/bbpress for blogging and community.

I’m working in Perl, so I also use the Perl test environment to do a mix of test driven development and ad hoc development (depending on where I am in a particular set of modules). As code matures, I tend towards test driven development.