Quote:
Originally Posted by kgzak
Along with what davidthefat said, maybe your coach/mentor will give you a copy of LabView so you can play with that at home. Thinking like a programer might be the hardest part. I picked up on LabView, and other languages, very easily because I already thought like a programer, I just didn't know it. Have your programer show you some code and explain what it does and soon after you understand how that works try to decode some code without having the programer explain it. I worked with one of you programers at Kettering when we had issues with our watchdog, he knew a lot about LabView and he would be a good person to talk to. How did he pick up LabView?
|
Luckily, I managed to grab a copy of LabVIEW for my laptop at home. You probably talked to another one of our programmers, who knew C++ and Java already if I remember correctly, so he just spent the '09 season messing around with LabVIEW and picking it up.
I'll definitely try trying to figure out code, probably from the examples included with LabVIEW (I can't have access to the competition code we used right away).
The real thing I want to do is learn more about "real" programming - CLI - than transition over to LabVIEW. I also have a question: Would it be better to learn C first, or C++? C is a good basic language, I hear, but C++ is more commonly used.