Skip to content

Instantly share code, notes, and snippets.

@worace

worace/sab.markdown

Created February 19, 2016 20:24
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save worace/8d4d3d3886c2ba11a810 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save worace/8d4d3d3886c2ba11a810 to your computer and use it in GitHub Desktop.
Download ZIP
Student Advisory Board 2/18
Raw
sab.markdown

Student Advisory Board 2-18-16

General Themes

  • More satisfaction with posse challenge -- smaller challenges and more lighthearted review process make people more engaged and leave time for additional work / bonding
  • Still some concern over large posses -- large groups make it hard for everyone to participate
  • General discussion around tone and focus of protocol -- would like sessions to get a little heavier on content (e.g. blog session -- could have dived more specifically into technical writing / how to write about code or other technical topics)
  • Some suggestions to shorten the time or mix in some "hard" skills -- e.g. 1/2 time on a soft skill (DTR, writing, etc), 1/2 time on applying it to your project or to a specific technical problem
  • Programming still hard
  • Turing still fun
  • Turing still lot of work

Mod 1

  • feel like group is bonding and coming together
  • some students going to union station to work together
  • some students still feeling lost, esp. on projects -- hard to find direction / get started
  • happier with posses -- able to contribute to the challenge more and it feels less overwhelming
  • some questions around time allocation of protocol sessions
  • calendar is already crowded so having an additional session monday afternoon needs to feel esp. worthwhile
  • difference in tone b/t rest of turing and protocol sessions

Mod 2

  • like rails
  • like all the repetition
  • appreciate andrew giving lots of feedback during project evals
  • protocol feelings generally "meh" -- not feeling excited for it
  • felt like more technical content could have been worked in -- blog session was too introductory

gear up

  • new format has been hit or miss

  • some people really liked the lady from last week, some felt it was too formal

  • pairin gear up got generally negative feedback

  • lady from last week did well at framing the discussion to be productive

  • some nervousness about protocol "working its way into portfolio" -- now soft skills are something you have to do

  • Rant: lately things are more (too?) serious around school -- instructors seem more reluctant to joke around (is this true?)

  • "sudden shift in culture" -- more structured, more hand-holding, more like grade school

  • "things that should be 'genuine' are turning more structural"

  • lengthy sessions are overkill on things we are "already good at"

Mod 3

  • posse challenge was a better difficulty level this week -- more time for other posse stuff
  • apis are painful
  • frustrations with omniauth / vcr testing
  • would like more clarity on which struggles are intentional / expected and which are incidental
  • would like more instruction on testing with APIs
  • some lessons running short -- could use this extra time to cover more material
  • "lessons come after we already figured it out"
  • suggestion: bring back TIP in small groups of 3 -- each monday solve a tech interview problem in a small group; instructors circulate around space and give feedback

Mod 4

  • no survey this week
  • people stressed from projects/jobs
  • some discussion around being able to spend more time refining/refactoring code on projects (project demands don't allow time for this)
  • People seem to be gaining job traction -- more interviews and responses happening
  • felt there was more interest and participation in posses this week
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment