Skip to content

Instantly share code, notes, and snippets.

@ckaminer

ckaminer/2018 Compozed Organized Learning.md

Last active June 28, 2018 20:00
Show Gist options
  • Save ckaminer/d5c50cde3fc0fa99be08fc476e027d94 to your computer and use it in GitHub Desktop.
Save ckaminer/d5c50cde3fc0fa99be08fc476e027d94 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
2018 Compozed Organized Learning.md

Hey team,

After experimenting with different types of learn days over the last year and gathering feedback through lab and team retros, we (myself, Ryan, Dana, and Zach) have put together a plan for our organized learning in 2018. Last year, we ditched individual learn days in favor of super learn days in order to make them more of an "event" and practice skills that stretch beyond our technical arsenals. These were awesome...but they required a ton of work to put on that we found to be unsustainable for a lab of our size. We all talked at our last lab retro about the desire to work across teams (AE and ARS). The plan we put together should hopefully alleviate some planning while fulfilling goals towards technical and personal growth. The idea for 2018 is to have a 3-month rotation between individual learn days, super learn days, and a hackathon. Below are the dates and ideas behind all three. Hopefully we can follow through with this ongoing experiment and get a feel for what works and what doesn't.

Organized Learning Trello board: https://trello.com/b/ecoerAqq/compozed-clt-organized-learning

Individual Learn Days:

  • Dates: January 5th, April 6th, July 6th, October 5th
  • Individual learn day
  • Share with your team what you intend to learn that day (don't show up day of with nothing planned!)
  • EOD put together a short post for #today-i-learned in slack

Super Learn Days:

  • Dates: February 2nd, May 4th, August 3rd, November 2nd
  • At least one presentation per person per year (No way to enforce this, but we think it would be really great to get everyone experience presenting their awesome learnings)
  • Suggestion: Use the individual learn day the prior month to learn something new and prepare a presentation on it (no out of office work required)

Hackathon:

  • Dates: March 2nd, June 1st, September 7th
  • Split into teams to work with people on other teams
  • Pick three projects (one per team) before first hack day to work on during ALL three days
  • Talked at last lab retro about making lab utilities, potential starting point for project ideas
  • Team presentation at end of hack day

NOTE: No December date; will be used for volunteer opportunity

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