View Single Post
  #9   Spotlight this post!  
Unread 21-09-2006, 10:59
Dave Flowerday Dave Flowerday is offline
Software Engineer
VRC #0111 (Wildstang)
Team Role: Engineer
 
Join Date: Feb 2002
Rookie Year: 1995
Location: North Barrington, IL
Posts: 1,366
Dave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond repute
Re: Software Team Organization

Quote:
Originally Posted by Orborde
Assuming you can FIND the code next season...
I think you already have the answer to that. Use Subversion. We keep all our code in there. As a rule of thumb, for the most part commits are only made when the code is tested and working (exception is when two different people are working on separate parts and need to merge them, then one might commit non-working code so that the other can merge and commit the merged working version right after).

The other thing we do is keep what we call the "motor spreadsheet" in Subversion. This is an Excel sheet that contains information on all the motors, sensors, etc. in the system and indicates what inputs or outputs they are hooked to. The electrical team maintains this sheet and notifies software if they change anything. Also we tend to stick with the same assignments year-to-year as much as possible (for example, drive motors are PWMs 1-4, etc). Once a motor or sensor is assigned to an input or output, it usually stays there for the season unless there's a really good reason to change it.