Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Perfect Coding Test

Be66f1ccc28a6a3dfb248454b8513b17?s=47 Ryan Bigg
October 25, 2017

The Perfect Coding Test

Be66f1ccc28a6a3dfb248454b8513b17?s=128

Ryan Bigg

October 25, 2017
Tweet

Transcript

  1. #ryry

  2. Culture Amp Junior Engineering Program

  3. None
  4. None
  5. TEST FOR YOUR DOMAIN (please)

  6. Domain: Surveys

  7. Step 1: Build a Rubric

  8. Rubric?

  9. • Adherence to the Ruby Style Guide • Clean and

    simple Ruby code • Code that works if the test requirements changed Rubric Core
  10. • Knows Array methods like count, detect, select, any?, none?,

    etc. • BONUS: Refactors common logic between methods into separate methods Extra
  11. Step 2: Model the Domain

  12. None
  13. Step 3: Build Challenges

  14. • Response.for(responses, user) — should use find or detect Rubric

    Samples responses.find { |r| r[:user] == user } result = nil responses.each do |response| if response[:user] == user result = response end end return result
  15. Step 4: DIY

  16. • Does this test against the rubric? • Would this

    be easy to understand for someone unfamiliar with the domain? • Am I tesXng at the right level? QuesXons
  17. Step 5: Get Feedback

  18. • What did you find easy? • What did you

    find hard? • Would you change anything? QuesXons
  19. Step 5a: Fix everything

  20. Step 6: Send it!

  21. Step 6a: Wait

  22. Step 7: Review

  23. Step 8: Give A.S.K. Feedback

  24. A.S.K? Ac"onable Specific Kind

  25. Feedback must be A.S.K.

  26. “The feedback provided is very valuable informa"on which will help

    me improve for future interviews.” “I wanted to say thank you for the detailed feedback that was supplied for the coding challenge.” “Thank you for your feedback, I feel like I’ve already learned a lot from it.”
  27. Rinse, repeat.

  28. QuesXons?