|
Re: The "Right" way to program
I would have to say working with somebody who also knows how to program helps. If you do something have them go through and check your work and do the same for them. If I had done this before Buckeye regional this year, a whole lot of chaos thursday would have been avoided. Trial runs work as long as you check the whole thing even if you change something small. I had used a variable twice for two different things in one of the earliest versions of our code and only checked the parts separately so when both parts ran the next week it freaked out. Learning from your mistakes also helps alot =)
[[09 was my first year programming as well.]]
__________________
WHAT TIME IS IT? TWO SEVEN NINE!!! [Team B =) ] Awards: 4 Safety, 2 Ind. Design, 2 Xerox, 1 Nat. Champs
2009 Buckeye Semi-Finalists (1014 & 695) || 2008 GLR Safety Award || 2006 GLR Safety Award
2005 Buckeye Regional Champs (67 & 274) & GM Industrial Design Award & Safety Award GLR Quarter Finalist & Xerox Creativity Award & Safety Award National Xerox Creativity Award & Curie Quarter Finalist (1126 & 180)
2004 Buckeye Delphi Driving Tomorrows Technology Award & Quarter Finalist GLR Champs Nationals Curie Division Finalist
2003 GLR GM Industrial Design Award || 2001 National Newton Division Winner & National Champions
2000 MI DaimlerChrysler Team Spirit Award
|