Re: 2016 global brainstorm
 

So can only "good" teams have good ideas? It doesn't take a perennial powerhouse to offer up information that some teams could find valuable. This coming from somebody who led an Ri3D team last year and is going to do so again this year. I'm not from a perennial powerhouse, nor do I consider myself to be an "expert" in FRC. However I've talked to a number of people who said our Ri3D robot inspired them. I do think a lot of the discussion this is designed to host is already done on Chief Delphi, but who am I to tell somebody that their idea (which is just trying to better the FRC community) is no good. Instead I'll offer a piece of advice that I think will improve the idea and differentiate it from forums that are already out there: maybe set up a system where people who sign up to do this get randomly placed in a Google hangout sessions with other random people who sign up. Maybe in groups of 5 to 10? This allows for inter-team communication and brainstorming, but isn't just a forum that people post on. It allows face to face communication (computer screen to computer screen... whatever) which other sites don't offer. Just a suggestion, like I said previously, I hope this is a huge success and good luck!

Re: 2016 global brainstorm
 

That's a nice idea! I'll try to do this :)

Well thank you :)

Re: 2016 global brainstorm
 

The "good" teams aren't going to share their strategy anyway, so it's not like the young teams were "learning anything important" regardless of this discussion. What would they learn watching good team release videos, that they wouldn't learn by discussing with other teams also?
Randomized hangouts discussions sounds really cool.

Re: 2016 global brainstorm
 

Would you guys prefer a system of randomized hangouts or a system where you choose a subject (programming, strategy, robot systems (drive trains, claw for example) ) and get in a room of people already talking about that subject?

Re: 2016 global brainstorm
 

Depending on how many people you have, and your available programming talent level, you could do both. Pick a subject, land in a random room discussing that subject.



Me personally, I'll probably be chilling with my team and the rulebook, figuring out just what pesky rules I gotta enforce THIS year (and a big thank-you to all the teams who brought correct numbers on the first try this last year!) and reminding the students to read the manual--and then watching CD and issuing the same reminder.

Re: 2016 global brainstorm
 

That would get my vote. I don't want to be stuck in a room full of programmers. :P

Re: 2016 global brainstorm
 

*gasp* :ahh:

We aren't that bad ya know.. ;)

Re: 2016 global brainstorm
 

Sorry bud you're living a dream :p

Re: 2016 global brainstorm
 

I agree!

Re: 2016 global brainstorm
 

I'm a programmer myself and even I wouldn't want to be in a room full of programmers. Just thinking about it is scaring me.

Re: 2016 global brainstorm
 

That's true :) I don't know about you but I prefer to be the only programmer on a project... I find it so much more efficient! But I need to get used to working with a team... :(

Re: 2016 global brainstorm
 

Many people prefer working by themselves, but the advantage of working with others and working with rookies is that you will pass your knowledge down to them while working so. This is important especially for seniors in a team to make sure to work with rookies and members who will still be on the team next year in order to pass their experience down to others. Mentors will always be there to help as well, but its important for students to mentor/help/work with other students as well. The students who teach newer members also gain experience, so its a benefit for all. Making sure seniors pass down their info to younger members is also key for team sustainability.

Also, working in a team environment is great experience for the work force. Your going to have to learn to work in a team eventually outside of FRC as well.

Re: 2016 global brainstorm
 

Man, you won't like the professional world then... A cube farm as far as you can see, filled with nothing but programmers!

All kidding aside, I know plenty of ways something similar to this happens on a small scale after kickoff all the time. To give just one example, there's a group of local area mentors that get together regularly throughout the build season - we talk about our impressions of the game, robot designs, and what we're having trouble with, all so we can mutually support each other and keep all of our teams on a successful path. Mentors from maybe a dozen teams are involved, and not only is it a lot of fun, but you hear about stuff you never would have imagined!

This brings it to a much larger scale, which is great. I would recommend largely separating students from mentors in the discussion, though, maybe with some sort of regular summary available as a go between for the two groups. From my experience, excitable mentors have a tendency to drown out students, and our concerns may be different - while the students want to figure out what to build, mentors are often looking more at how to build different aspects and the problems they'll encounter later on in weeks 4/5. I know I, personally, would rather be involved in discussions with other mentors specifically so I can figure out the landmines awaiting us. My team will come up with the design they see fit, they don't need me involved too much with strategy or overall capability design:)

Re: 2016 global brainstorm
 

I can't figure how to split the two groups without completely isolate them... :ahh: It's a good idea though!

Re: 2016 global brainstorm
 

40 teams signed up! That's pretty cool :) Any suggestion on what to use to build the site?