Quote:
Originally Posted by eagle33199
We've been around for 3 years now... And i can tell you that the teams that win are the teams that keep it simple. Simple autonomous modes work just as well as complex ones, once other robots start bumping into you. Just being able to drive around can get you into a winning alliance.
|
Fixed, you may view the winning teams' robots as complex but if you look at most of the teams that consistently win it isn't a complex mechanism but a series of simple mechanisms and systems that work together. Simplicity wins. Remember that in code too, yes I can write a function that takes 40 arguments and is 400 lines long. Should I? NO! Break it into a dozen small functions not only will it make it easier to write it will make it easier to change for when the wrench monkeys decide they want to change the whole robot.
Us code monkeys need to remember that what we do is the least flashy, least recognized, least understood, and most important part of any robot. It is also among the hardest thing in FRC (I am factoring in time allotted to this task).
I hate to recommend a bad habit but in a lot of cases what stresses me out when doing FRC code is the people who know nothing or very little about programming telling me how to do my job. Just acknowledge them, say you will look into it and move on. Sometimes they have a good idea but it is ALWAYS simpler to not explain why they are wrong. Trust me, it will lead to far less arguments.