|
Re: Architecture for software
Our team created a patterns and practices document because we have a total of nine programmers this year. It drew out some simple and easy to follow guiedlines for commenting our code as well as the naming of variables constants, and alliases. While we try to create alot of pc programming projects (scouting software, etc) to keep our programmers busy durring the build season (to many people working with the RC just slows us down), the supreem law of the land on our team is that no programmer should have nothing to do because he/she can always doccument their code better.
-Don
__________________
Team 548:
Attending National Championship, Genesee District, Detroit District 2, West Michigan District, Michigan Championship?
|