View Single Post
  #1   Spotlight this post!  
Unread 30-11-2016, 10:05
Monochron's Avatar
Monochron Monochron is online now
Engineering Mentor
AKA: Brian O'Sullivan
FRC #4561 (TerrorBytes)
Team Role: Engineer
 
Join Date: Feb 2007
Rookie Year: 2002
Location: Research Triangle Park, NC
Posts: 886
Monochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond repute
Re: Team Structure and Build Schedule

I'll offer the general comment that you should allocate more time for most things that you have on there. For instance you only 1 week of actual robot programming. Often programming projects work by programming small chunks at a time, testing them, and them moving on. Other times people try to write a bunch of code up front and then do a bunch of testing afterword (not what I recommend). But either way there will be a ton of code writing all throughout the process. Considering that you are teaching students week 1, I might allocate 3 or 4 weeks to programming on the actual robot.
__________________


2016 | Innovation In Controls, Industrial Design, Quality Award, NC District - 4th Seed
Reply With Quote