|
Re: Amatur Team
Definitely take a look at the javadocs included with WPILibJ. They help quite a bit. As for any issues you may come across, go along with the usual principals such as isolating the problem, etc. And always remember to test changes, even if they seem minor. Changing one line of code might just break something. And on less of a programming level, don't feel hurt if/when your team blames you for a problem. It's generally not personal, and it happens a lot since it's apparently pretty easy to blame the code. If something goes wrong, you should look over your code just to make sure there's nothing wrong there, even if you're completely positive that everything you wrote is correct. And sometimes, you'll get someone insisting that you should check the code for problems when it's something remedial such as printing values from a sensor. At that point, just nod and pretend to look it over. If it's really something that can't be wrong, there's no sense wasting time fighting over it.
|