Is your team ready ?
 

TEAM 5920 is excited and ready for the 2017 Challenge.

Re: Is your team ready ?
 

I don't think anyone is truly ever ready :ahh:

Re: Is your team ready ?
 

"Chance favors the prepared mind..."

Re: Is your team ready ?
 

There is always so much more you can prototype before season, so much more you can practice and so much more you can learn! I think each sub team could have another 2 months and not truly be where we want. Programmers made the leap to C++ this year and could use more time to learn. Business team is still in the process of finding us a potential build site due to a possible eviction (our sponsor's building got sold so it is owned by different people). Myself and a mentor (build team) recently set up and repaired a roughly 50 year old Miller TIG welder, creating a redneck water cooler (55 gallon barrel with a small little water), so there is so much more practice we could use to actually refine our aluminum welding skills. If you've TIG welded aluminum, you understand it's not the simplest thing to do, especially on a 50 year old machine :yikes:

All in all, I'm pretty sure the team is hyped! This is finally the water game year because ya know, it takes water to make steam ;)

Re: Is your team ready ?
 

Our team typically does very little pre season prep, just new programmer training and teaching tool safety. We will however all be coming together tomorrow for the reveal and, yes, we are all tremendously excited!!!

Re: Is your team ready ?
 

May I ask why your team jumped from C++ from what I assume is Java?

Re: Is your team ready ?
 

Nope.

Re: Is your team ready ?
 

Nnnnnno

:eek:

Re: Is your team ready ?
 

:confused: What is ready? What is a team? What is mine? What is?

It isn't even build season yet and I'm too tired/excited/overwhelmed to know words.

This thread should help: https://www.chiefdelphi.com/forums/s...d.php?t=136265

Re: Is your team ready ?
 

Ready for what? Something happening?

Re: Is your team ready ?
 

Not the same person, but my team went from C++ to Java last year (so other way around if they started on Java). We did this for a few reasons: (1) There seemed to be more material online for people to learn from, (2) I personally feel it's easier to teach to a complete beginner, and (3) it aligns with AP CS curriculum, which is just sorta a bonus because students don't have to bounce around between the two every day in class then in the lab.

However, I think it's more likely they moved from LabView to C++. A lot of teams are originally on LabView because their programmers can't totally program prior to the season and decide there's not enough time to learn a language which has a much larger learning curve for a beginner (not to say that's why all LabView teams are on LabView though). I know of a lot of teams that decide during an offseason or when they gain a programming mentor they might not have had to move to a more "conventional" programming language, which I personally think is awesome. I view LabView the same way I view GRIP, where it's an amazing tool if you just want to get things done quickly or don't have the proper tools for the alternative, but personally feel the learning experience of using Java/C++/Python is a lot greater.

Hope that wasn't coming across as a diss of LabView or teams that use it, I think it's great if you use it and hold nothing against it. Just feel it's awesome when teams move to languages that are more widely used in industry that present their own issues which you have to figure out.

Re: Is your team ready ?
 

Due to having a small team in the past, and nearly a rookie team last year, we used LabView to make programming simple. My father who is the programming mentor does coding for Apps and such, and strongly disliked LabView (along with our programmers), so we went to Java over the summer. A couple months back, we attended a conference hosted by Stryke Force (2767) and they talked about how Java made it more difficult for some things due to the garbage collector. Although there was other reasons, the team decided to switch to C++ since some of the members were familiar with the C language. That is as far as I know, I am not on that sub-team so I am not sure the other reasons.

Re: Is your team ready ?
 

Thursday's (nominally) build session was spent with Rookies for Dummies, review of our (pre-kickoff) GANNT chart, and a bunch of other technical and administrative details -- and a Maori war chant. If we ain't ready now, we ain't never gonna be ready.