Thread: Software Team Organization
View Single Post
  #12   Spotlight this post!  
Unread 21-09-2006, 20:35
Astronouth7303's Avatar
Astronouth7303 Astronouth7303 is offline
Why did I come back?
AKA: Jamie Bliss
FRC #4967 (That ONE Team)
Team Role: Mentor
  
Join Date: Jan 2004
Rookie Year: 2004
Location: Grand Rapids, MI
Posts: 2,071
Astronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud of
Re: Software Team Organization
Even with our small team (myself), I have been doing a lot of that for some time. Especiall #1, 4, 5.

It's notable that you almost have to make an exception for #4 for interrupts. (Still use the alias for value access, but you don't have to alias all the configuration bits.)

The lines of communication between the software group (me) and head of electrical (Biff) have been open. We have always worked closely.

One thing we have gotten to doing is to define what each of the IO pins are, and how the sensors are wired to those pins. eg, have pwm01 and pwm02 go to the driveline and digIn1 and digIn2 go to the encoders. Define which way pots go. (I recomend the same direction for the pot, the motor that drives it, and any control board for it.)

BTW, Subversion can fail commits with helpful messages. (See the mime types commit hook floating about.) You don't have to email a team member to notify them of bad practices.

All-in-all, very good.