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

The Perfect Coding Test

Ryan Bigg
October 25, 2017

The Perfect Coding Test

Ryan Bigg

October 25, 2017
Tweet

More Decks by Ryan Bigg

Other Decks in Programming

Transcript

  1. #ryry

    View Slide

  2. Culture Amp
    Junior Engineering Program

    View Slide

  3. View Slide

  4. View Slide

  5. TEST FOR
    YOUR
    DOMAIN
    (please)

    View Slide

  6. Domain: Surveys

    View Slide

  7. Step 1:
    Build a
    Rubric

    View Slide

  8. Rubric?

    View Slide

  9. • Adherence to the Ruby Style Guide
    • Clean and simple Ruby code
    • Code that works if the test
    requirements changed
    Rubric Core

    View Slide

  10. • Knows Array methods like count,
    detect, select, any?, none?, etc.
    • BONUS: Refactors common logic
    between methods into separate
    methods
    Extra

    View Slide

  11. Step 2:
    Model the
    Domain

    View Slide

  12. View Slide

  13. Step 3:
    Build
    Challenges

    View Slide

  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

    View Slide

  15. Step 4: DIY

    View Slide

  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

    View Slide

  17. Step 5:
    Get Feedback

    View Slide

  18. • What did you find easy?
    • What did you find hard?
    • Would you change anything?
    QuesXons

    View Slide

  19. Step 5a:
    Fix everything

    View Slide

  20. Step 6:
    Send it!

    View Slide

  21. Step 6a:
    Wait

    View Slide

  22. Step 7:
    Review

    View Slide

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

    View Slide

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

    View Slide

  25. Feedback must
    be A.S.K.

    View Slide

  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.”

    View Slide

  27. Rinse, repeat.

    View Slide

  28. QuesXons?

    View Slide