Skip to content

Conversation

socksy
Copy link
Member

@socksy socksy commented Sep 27, 2017

Main changes:

  1. Reduced intro round
  2. Put "no sexism" and "don't insult people's tech" stuff out from the discussions to near the beginning
  3. Changing order of the discussions, the questions at the beginning all together, the ideas/answers separately
    • This is in order to get people to come up with them in smaller groups on paper, then check how they compare to our answers afterwards
  4. Move CoC violation into "Know what's up" ideas/answers
  5. Add a little placeholder about the curriculum


## Please take a look :)

# Some people are trialing a new Curriculum

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: lowercase c

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"slideshow that goes through the concepts....and then people play with Quil"?

@socksy socksy requested a review from vsmart September 27, 2017 22:19
@nblumoe
Copy link
Member

nblumoe commented Sep 28, 2017

Looks good to me! 🙌

@daveliepmann
Copy link
Contributor

Nice work. I particularly like how you moved the discussion slides around. I say merge.

One tiny thing I would consider is to mention that the curriculum is a bunch of syntax/data structure/control flow slides followed by playing in Quil.

<li>What's your favorite place in Berlin?</li>
<li>What's the most non-coding thing you do?</li>
<li>What's your name and pronouns?</li>
<li>Have you been to a ClojureBridge or similar workshops before?</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I liked having one other non-programming related question. Maybe "fun fact about yourself" or "your favourite restaurant" or something. Or even "how did you hear about ClojureBridge"

Copy link
Member Author

@socksy socksy Sep 28, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reaosning behind this was that the whole time before you speak, you are worrying about what to say, and barely remember other people's answers anyway... At the same time, this part is also takes a while, so it's nice to be able to reduce it to a friendly names round.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in favor of shortening it, but I hear Franka's point about keeping one (and only one) non-programming question. I vote "favorite place in Berlin" because it's easy and revealing without being intrusive.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given there are gonna be people not from Berlin there, I suspect another one would be better (fav. restaurant?) Though I am still personally skeptical about having it

<h2>Coaching: Build a Team</h2>

<ul>
<li>ClojureBridge normally makes a distinction between coaches and TAs (teaching assistants).</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 For removing this

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -0,0 +1,253 @@
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was checking in this file on purpose?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely. I have another branch for it which I was wondering if I should make into a different PR. Not having it means I can't compile the site, which was really very frustrating.

@vsmart
Copy link
Member

vsmart commented Sep 28, 2017

@socksy LGTM. I left some small comments. Thanks for going through and streamlining this.

@vsmart vsmart mentioned this pull request Sep 28, 2017
@socksy socksy merged commit 2cc3c81 into master Sep 28, 2017
@vsmart
Copy link
Member

vsmart commented Sep 28, 2017

Thanks @socksy! I think this change of order worked really well! :D

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

Successfully merging this pull request may close these issues.

5 participants