Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ Page #10

Open
HipsterBrown opened this issue Jan 8, 2016 · 6 comments
Open

FAQ Page #10

HipsterBrown opened this issue Jan 8, 2016 · 6 comments

Comments

@HipsterBrown
Copy link
Collaborator

Before attending a Nodebots event, there might be some frequently asked questions we can address up front. Some that come to mind:

  • What's the difference between the two event tracks?
  • What should I bring?
  • Do I need to know about robots already?
  • Do I need to be a JavaScript wizard to understand the event?
  • What's a Nodebot?
  • What kind of topics will be covered?

We can create a separate page to cover any questions constantly come up at events or about the events. If a question isn't covered, we can link to the repo's issues page for people to ask there. AND/OR link to the BoroJS #nodebots Slack channel.

@reconbot
Copy link
Member

reconbot commented Jan 8, 2016

So.. I propose.

  • Track 1 would be a smaller hack on stuff event at bocoup with our lab equipment. ~15 people, one or two quick presentation to show off something someone has learned.
  • Track 2 would be a larger workshop event. We have about 40+ Sparkfun inventor kits with arduinos, we'd teach basic electronics and johnny-five. This gets the person and their computer ready to do anything.

Every single nodebots event from last year (That @acingraham, @rwaldron and I ran) included a 5-10 person circle that did a blinking lights example. (Usually had about 15 - 20 people.) So I think this might be a good split. People who don't need the intro get to share and hack, people who do get to learn together.

There are plenty of cons however. Alternatives might be doing the beginner workshop a few times with 15 people.

I'd like to have a conversation about what people think of the two track proposal.

@byronhulcher
Copy link

I'm more interested in Track 1 (getting time to show off + feedback and tips) but I took advantage of a Track 2-style workshop in 2015 and that was so invaluable and eye-opening! I can't offer up a space but if its a matter of human resources I'd be happy to volunteer to help run a larger event.

@ArmandoAmador
Copy link
Collaborator

I like both track.

Maybe we can split a night into having a hack and tell type format and then
a workshop session. This will allow us to introduce nodebots to people who
want to get started.

On Friday, January 8, 2016, Byron Hulcher [email protected] wrote:

I'm more interested in Track 1 (getting time to show off + feedback and
tips) but I took advantage of a Track 2-style workshop in 2015 and that was
so invaluable and eye-opening! I can't offer up a space but if its a matter
of human resources I'd be happy to volunteer to help run a larger event.


Reply to this email directly or view it on GitHub
#10 (comment)
.

@reconbot
Copy link
Member

reconbot commented Jan 9, 2016

The splitting of events is mainly due to bocoup only sitting 15 people with tables and power.

@acingraham
Copy link

I'm an organizer for the NY JavaScript Meetup and we've had a lot of
success by having different tracks of events and then having each event be
somewhat specialized. For example, rather than repeating the identical
intro event each time, an intro event could focus on a particular component
(e.g. LEDs, servos, pressure sensors) or building a project (e.g. sumo bot,
an LED whose color reflects current weather conditions, electronic dice).

Additionally, at NYJS we rely heavily on trial-and-error to figure out what
works. I see no problem with starting with the 2 tracks Francis mentioned
and iterating on them as we get feedback and trying different approaches as
ideas come to us.

@reconbot
Copy link
Member

Yeah, it's working out so far, we should probably make this page now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants