I'm a new programming mentor. I tagged along with the team for summer events, but didn't get really involved until last fall.
Quote:
Originally Posted by Greg McKaskle
Why not release SW earlier?
|
I'd like earlier releases. The WPILib is Open Source and new mentors probably become available to help with development and training in the fall. I didn't even know we had to sign up for a beta until it was too late.
The majority of the toolchain is commercial off-the-shelf so release date won't matter. Unless it's a water game. (ha! even noobs know about that joke)
Quote:
|
Why does WPILib keep changing?
|
Because it's not dead. The problem domain is way too large to ever be solved, so the only way it'd stop changing is if everyone loses interest. I've only been working with WPILib for a couple weeks and I already have a huge TO-DO list. Robot Builder and Smart Dashboard move things in a good direction, but they are far from complete. Error handling, diagnostics, and testing don't really exist yet.
Quote:
|
Why isn't there default code?
|
Lots of teams put their code up in a public repo. I learned a ton from their generous examples. We will put our code up this year.
If someone wants to lead the development of an example or reference control system, I will help. I don't know enough yet to organize it. This would make a great off-season project for teams wanting to stay active without the pressure of a competition schedule.