Skip to content

Instantly share code, notes, and snippets.

@kimschles

kimschles/ideas.md

Forked from kylecoberly/ideas.md
Created May 22, 2018 02:24
Show Gist options
  • Save kimschles/a08e3c8fb47499742dac2f64f80d6bca to your computer and use it in GitHub Desktop.
Save kimschles/a08e3c8fb47499742dac2f64f80d6bca to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ideas.md

What do we do?

  • Outcomes and standards-based education
  • Not a curriculum company

Who is this for?

  • Turning juniors/mids into mids/seniors
  • Turning seniors into leads, principles, VPs
  • Not necessarily with career alignment- they don't have to go all-in
  • Technology-specific training

What kinds of things do they need to learn?

  • Testing
  • CS
  • Paradigms
  • Teaching- teach people our style and philosophy
  • Leadership
  • Not just coding- soft skills, product managers, etc.
  • Soft skills: Running meetings, clean repos
  • Being strong at meta-cognition

Assessment

  • Authenticity
  • Not code katas
  • "Build this thing with these requirements"
  • Base them off of big OSS projects
  • Interview-style assessments were high rigor
  • Group assessments (careful not to be gameable)- how well do you interact?
  • Diagnostic assessments
  • Procedural generation is the key to creating enough practices
  • Use # of practices passed without error as mastery, instead of high-stakes style assessments
  • JV version of the game
  • The whole game is there, even if they aren't playing it (supply the front-end for the back-end)
  • Multiple levels of assessment for the same topic
  • Isolate micro-skills for remediation
  • Real-time remediation - recommending skills to work on?
  • In-person interview portion
  • "Full-game" assessments, like coursework
  • Track progress with xAPI
  • Diagnostic assessments - "You think you know how to run a meeting? Most people that think that don't. Take our test and find out what you need to work on!"

Curriculum

  • Site licenses
  • Curation

Staffing

  • Burst up and down with a tiered contractor model
  • Part-time mentoring, ala Thinkful
  • 20-hour/week contracts for people to supplement a contracting pipeline

Location

  • Fully remote loses some community
  • Most things can be done remotely, though
  • Have rotating locations (sponsorships)
    • "We're at Charter this week!"
    • Like a meetup
    • Good for the sponsors, exposes them to people they might want to hire
    • No rent, mitigates risk
  • Commons on Champa

Real-Time Support

  • Tiered support at queue- student, who's on duty, everyone
  • Set the expectation- how long do you struggle?
  • Better onboarding- walk them through an imagined scenario

One Day Format

  • Should eventually be scalable down to one hour, gym-style
  • Need lots of context, ramping up, explanation of the format
  • Have videos, assesments, and materials prepped ahead of time
  • Need a trained staff
  • Reflection - "I hate this and don't want to do it"
  • Can I keep asking for help? Slack community, etc.
  • Limited menu of topics at different levels - 3?
  • Opening philosophy -> Orientation
  • Each topic should have a list of objectives, scaffolding, and should feel a little hand-holdy
  • You've come to 2 of these- hackathon?
  • "You've earned enough to participate in this next cool thing!"
  • The price of participation is doing all of the things
  • Advertise with testimonials
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment