Quote:
Originally Posted by Sean Raia
This.
You should definetly try to get in contact with other teams in Washington who have done this before. Even if they just send you some of last years code, it will give you something to work with.
|
Welcome!
Post any questions you have about FIRST related thing on the sub-forum that you think makes the most sense with the topic of the question, but its not too strict, just dont post a "broken gearbox question" under "programming", for example. And please use google or the search function on this forum before posting your question.
Now-
Most if not any team will be willing to help another team getting started. We are for the first time this year and are VERY excited!
Oh, and FWIW, it seems like the majority of teams start on labview and switch to a text-based language (Java, C++, Python (yes Python)) later on. This is probably because from what Ive heard, labview makes more sense to non-programmer (or not yet) types. We used Labview for two or three years before switching to Java, and we may switch to C++ again this year.
Personally, It annoys me, but I learned on C++ at least 5 years ago so the way text-programming "works" was already with me, so Im not a good indicator. Though, once you know one language, like Java, learning another like C++ is way easier than if you have no prior experience. I would suggest using labview until you feel comfortable using Java, which I believe is easier than C++ for a few reasons, A being just the way it looks, C code looks more complex than Java to me. B being the way memory is allocated to programming stuff, and how you deal with that.
So go get familiar with labview NOW (not at the kickoff
) but try to learn Java in your free time. But hey, if Java just isnt your cup of tea, that fine too, and theres nothing wrong with sticking with Labview. Many VERY successful teams out there do it.