Skip to content

Latest commit

 

History

History
79 lines (73 loc) · 5.19 KB

survey.md

File metadata and controls

79 lines (73 loc) · 5.19 KB

##ClojureBridge MN March 2014

1. How likely are you to recommend ClojureBridge workshop to a friend or colleague?

  • Very likely - 16
  • Somewhat likely - 1 (number 14)

2. What was great?

  1. People, clear (mostly) instructions, good food
  2. Friendly, helpful, mentors!
  3. I like the pace of level 1
  4. Welcoming to people at all experience levels. Event TAs had different experience levels, which was great! Also, the panel was great!
  5. The enthusiasm. Getting women together to work toward a common goal.
  6. How supportive everyone was.
  7. The amount of support from the TAs. And the food.
  8. I was very happy with the amount of things covered. The environment was supportive/friendly and not as intimidating as I expected.
  9. Organization and coordinating the event. Kudos! Also, plenty of food.
  10. The informal installfest help as well as the kindness and helpfulness of the TAs
  11. I won a free Clojure Programming Guide.
  12. Good (clear) instructions. Knowledgeable TAs that worked together to get us the answers.
  13. TAs were super helpful and kind!
  14. Everyone was really welcoming, friend and super helpful
  15. People getting excited about getting something working and the discussion panel.
  16. The helpful and friendly Tas!
  17. TAs were super helpful and nice

###3. What should we change?

  1. Do more of an initial overview for track 1 - what clojure is used for, it's basic syntax etc. Also, installfest didn't seem necessary - took me ~15 mins. But thanks for the pizza!
  2. Not sure. Maybe tables to sit at instead?
  3. It might be better to have a quick 30 minute explaining clojure.
  4. So much food! :)
  5. Remind people to use IM to communicate. Great idea, but it was forgotten.
  6. Nothing.
  7. With in the material, I suggest milestones - that way concepts are distinct and it allows for breaks in the work-flow/day
  8. The instructions should be impeccable - when there are typos, assume we don't understand it. Also, when people are finished, talking quietly helps those reading not to become distracted.
  9. Track 2: more explanation of syntax
  10. I would say that track 2 is for Experienced Programmers versus "experience with programming."
  11. Clearer and concise instructions for sample coding.
  12. I know people work at different paces (and learn differently), but I think it would be helpful to have some "lecture" on a topic, time for questions, then time to actually make the changes. Short of that, I would encourage participants to read everything in the instructions and type the code (rather than copy/paste). I know this will cause more mistakes, but that's a great way to learn!
  13. Curriculum has a few typos and it unclear in some spots.
  14. I feel like I didn't learn much at all about Clojure itself. I followed the instructions fine, but wished there was more instructions about what we were actually doing.
  15. A location with tables would make it easier to work together.
  16. The tutorial materials sometimes jump around, doesn't explain enough. Also, for a totally new person, a lot of big concepts. Likely to be a risk of copying and pasting w/out knowing/understanding what you're doing.
  17. Written instructions were confusing - seemed to jump (mini) steps

4. What else would you like us to know?

  1. Thank you! it was great to feel successful so quickly. Too many TAs?
  2. na
  3. Practical examples
  4. A room with actual tables might be nice for collaboration, but everything is donated, so I understand you can't be picky!
  5. Thank you.
  6. The food was fantastic. - thanks!
  7. One other suggestion in the material is to link back to previous task - we learned to create a branch and then later it said create a branch - linking to the original explanation would be helpful
  8. I liked that we could go at our own pace. I like to take my time reading and rereading. I appreciate the format.
  9. Gr8 job!!!
  10. I really appreciate the effort that was made to accommodate different preferences. (Food, learning styles, etc.)
  11. More information on bootcamps or trade schools providing certifications or degree programs.
  12. Thank you all so much for organizing this!! It was great. =)
  13. Thank you!!!! :)
  14. I liked getting to use git and feel like I have a decent understanding of that!
  15. na
  16. Thank you for all the work from the organizers and volunteers!
  17. :)

Random handwritten paper survey: (This might be from Brian Dawn regarding Track 2)

  • Agree on a subset of the syntax in the examples to not confuse people
  • Ensure every feature is preselected before it's used. +1
  • Simpler threading macro example
  • Acculomate with clojure limits
  • Limit column width to 70
  • Hack time is awesome
  • Pods, issue with room

Millie's Ideas/Summary

  • Maybe we should add to the survey who the primary TA was that was helping them. This would help us get a sense of the TAs that were really creating an impact.
  • Good git tutorial
  • Something for people who want more depth. Links to more information on the web?
  • Track one still needs some polishing. (Typos, milestones, how to balance self lead instruction with lecturing, copy pasting ok?, bigger concepts missed?, jumps around)
  • Track two framing. Who is this for?
  • Location with tables