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

Moar Coderetreats (Zero Overhead Coderetreats) #46

Closed
codecop opened this issue Nov 18, 2018 · 11 comments
Closed

Moar Coderetreats (Zero Overhead Coderetreats) #46

codecop opened this issue Nov 18, 2018 · 11 comments
Labels

Comments

@codecop
Copy link
Member

codecop commented Nov 18, 2018

As I said in the end of GDCR18 (#40) I would like to attend more Coderetreats. And who would not? ;-) Which means I have to make more of them. Here are my ideas for a format that is maybe more sustainable and which I would like to discuss with you to do so:

Must be minimal to no overhead for us as organizers

  • small group, 6 to 10 ppl max, =
    • 6 to 8 regular/repeating dojo or CR guests, +
    • maybe 2 newcomers (we can deal with them on the fly)
    • I want to limit public access, still be available to newcomers...
    • from my memory I count at least 20 repeating guests that might be interested (including you)
  • no big registration, no big fuzz, maybe a SWK event for registration. only trusted ppl, no money transfers
  • we agree to go to lunch together, either Kantine or restaurant nearby

No facilitator

  • we all know what needs to be done, many of us have run a CR themselves
  • instead of intro
    • inform us about the venue (fire exits etc)
    • see which languages we have around
    • we discuss the goal of the day and chose a topic, e.g. OO or FP
  • after session we discuss in a circle again and choose next constraint for us and according chosen topic

Open Questions

  • frequency: one such CR every 3 months? maybe even every month? sure not everybody will be free each time, still it is about creating opportunities to learn
  • day - still Saturday? I am also available certain days in the week, as are some freelancers.
  • venue - venue is always the problem, but a room for 10 = 5 pairs should be easier to get that 40...

Please let's discuss @dertseha @paulroho @mlem @duffleit @xbojch @goerge

@paulroho
Copy link
Contributor

Peter, I love your proposal.
It would be way easier for me to attend during the work week than on a Saturday, esp. if we plan ahead for a longer period.

@dertseha
Copy link
Member

Thank you for your proposal.
I'm commenting here to mark that I have read it and will think about it - yet I don't have an immediate, streamlined answer.
Various thoughts that come up at the moment are conflicting and deal more with my own situation rather than your idea.

@mlem
Copy link
Contributor

mlem commented Nov 20, 2018 via email

@xbojch
Copy link
Contributor

xbojch commented Nov 20, 2018 via email

@dertseha
Copy link
Member

So, yes, good idea. I'd be interested to join, assuming a bi-monthly occurrence (as an example, I guess it'll be either 6x or 4x per year). Also, to keep Dojos as the small, regular variant, and these retreats an upcoming chance.

Side comments at this point: Thomas, who is a regular guest, told me to prefer Dojos rather than retreats, as these retreats are too exhausting. Also, compare to shrinking participation on last retreat, especially for sessions 5 and 6 - so a reduction to 4 sessions might be an option. (e.g. two before, two after lunch)

Now my conflicting thoughts:
When I spearheaded the dojos years ago, I did so to finally be able to have them regularly, and be able to join as a participant. Under this perspective, I've succeeded, because I'm hardly organizing Dojos (nor retreats) anymore, and I am free to participate - even occasionally skip some. At this point also my big thank you to you all for making this possible!

Though, with all these possibilities - and learning along the way - I've reached some sort of foggy glass-ceiling. The more and more specific various learning points are, the less I am in situations where I can apply them. Hence my shallow answers at the last retreat, culminating in having no answer to what I'd do different next day.
Note, on this public forum I'll not get into details about my current work position.
From my private position though I can also say that I see myself too much in development topics - and at some point I'd also like to live a life apart from code. Especially if, whatever I learn, has (next to) no option to become practice.

Folded back again to these retreats: Yes, I'll join, though I don't have much to give or "actively take away" - apart from my enthusiasm :)

@dertseha
Copy link
Member

Addendum: Having said all of that, this is more of a consumer-view. If, however, I already have some things that others would like to know about, then we'd have a provider-view - and I'm always happy to tell/teach others (willing to listen) about stuff.

@codecop
Copy link
Member Author

codecop commented Nov 21, 2018

@dertseha I guess you can always bring Go to the table, and C++ of course.

@goerge volunteered to run the first instance, in 4 weeks, last week before Xmas (17 to 25th Dec)
We still discuss the day of the week. During week is easier for some ppl. Rooms are easier to get on Saturday.

@codecop codecop changed the title Moar Coderetreats Moar Coderetreats (Zero Overhead Coderetreats) Nov 21, 2018
@mlem
Copy link
Contributor

mlem commented Nov 23, 2018 via email

@codecop
Copy link
Member Author

codecop commented Nov 23, 2018

@mlem please go ahead with the Dojo. Different events. Different guests.

@codecop
Copy link
Member Author

codecop commented Dec 9, 2018

After discussing with @dertseha I decided for a schedule of every third Saturday every second month. So the days are known long time in advance. I stayed with Saturday because it is easier to get a room for us then. We might shorten the CR to 5 sessions if needed, we will see.

I created a session ticket, see #48 to manage them.

@codecop
Copy link
Member Author

codecop commented Jul 1, 2019

This seems to run for now. Closing

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

No branches or pull requests

5 participants