• Adherence to the Ruby Style Guide
• Clean and simple Ruby code
• Code that works if the test
requirements changed
Rubric Core
Slide 10
Slide 10 text
• Knows Array methods like count,
detect, select, any?, none?, etc.
• BONUS: Refactors common logic
between methods into separate
methods
Extra
Slide 11
Slide 11 text
Step 2:
Model the
Domain
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
Step 3:
Build
Challenges
Slide 14
Slide 14 text
• 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
Slide 15
Slide 15 text
Step 4: DIY
Slide 16
Slide 16 text
• 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
Slide 17
Slide 17 text
Step 5:
Get Feedback
Slide 18
Slide 18 text
• What did you find easy?
• What did you find hard?
• Would you change anything?
QuesXons
Slide 19
Slide 19 text
Step 5a:
Fix everything
Slide 20
Slide 20 text
Step 6:
Send it!
Slide 21
Slide 21 text
Step 6a:
Wait
Slide 22
Slide 22 text
Step 7:
Review
Slide 23
Slide 23 text
Step 8:
Give
A.S.K.
Feedback
Slide 24
Slide 24 text
A.S.K?
Ac"onable
Specific
Kind
Slide 25
Slide 25 text
Feedback must
be A.S.K.
Slide 26
Slide 26 text
“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.”