Suggestions for moving from Labview to Java

[GeeTwo]

Jeff did a course in Java for our team a couple of years ago based on Java for Dummies. They basically worked through the chapters, with homework taken from the book early and custom WPIlib stuff after a few chapters.

[kingca]

Since they are beginners another great resource is codehs.

[mathking]

My first piece of advice is to take some simple working robot code (either sample code or from a team's public repository) and have your students examine it. Ask them to identify what and where for making simple modifications. If you are moving from LabView you have anyone who knows LabView, have them identify which parts of the LabView code correspond to which methods in Java code. Make a poster of this.

Robocode is a valuable tool if you have students with no Java experience. They program virtual robot tanks to compete against one another, using a simple, well-documented framework.

The best piece of advice I have is to take a working (mechanically and electrically) robot and have the programmers modify default code to make it drive. Then have them make it do something simple autonomously. Keep making incrementally more complicated tasks and have them work on those. And have them document what they are doing so they have references for use when they make the same mistakes during the build season.

Finally, ask questions. Lots of them. Here is fine but email tends to be a better venue for a lot of quick back and forth questions and clarifications.

[apache8080]

When moving to Java with a team with little Java experience, it is important to make sure the students know Java. One way that I learned Java and have taught new members Java is through Stanford's CS 106A introductory programming course(Link Below). This course helps teach students Java and also how to solve problems using programming. After students have learned how to use Java it is also useful to read other teams robotics code on github. I learned a lot about programming robots from reading 254's code on github.

Stanford CS 106A

Team 254 Github

[Dan Waxman]

To reiterate what others have said, I would definitely focus on teaching Java before you focus on any robotics concepts; it would be very difficult to read or write a book in Spanish if you don't speak any. After you get your students started on Java to a point where they can coherently read through other's code, then the FRC concepts come easy. There's very little to program that's difficult in FRC, and odds are if it's difficult, there's been a tool made to make it easier. So I'd just drive home that fundamentals are key.

As for how to teach, there's multiple approaches. Two mentioned before are codeacademy, which is a great resource, or academic class available online. Both of these are great options. Personally, the way I'd do it would be to teach during team meetings, and then supplement that learning with further learning online that you plan out, as well as incorporating challenges to mix in (codewars.com is awesome for this). Any questions feel free to PM me.

[CoachC]

Thank you all for your outstanding responses. I will utilize much of what has been suggested. I understand it will be a daunting challenge given my teams situation but I feel that if we get an early start the growing pains will be minimal. I have one student who is eager to learn and will be with our team for several years (a new programming captain in the making). Thanks again. Ill post our progress along with bumps in the road as things move forward.

Jim (Coach C)
Team 5247
Red Devil Robotics