summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormo khan <mo@mokhan.ca>2022-08-25 11:23:35 -0600
committermo khan <mo@mokhan.ca>2022-08-25 11:23:35 -0600
commitc9405c70b1046574dabeeb6e81a0ad0a65c98f7e (patch)
tree69f790268c9e18029cc6024f729eeda48d5b5cda
parent4070b5051ea7acff2185ccc210baa4ffaeb01235 (diff)
add note on test defects
-rw-r--r--learn/humans/README.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/learn/humans/README.md b/learn/humans/README.md
index 4a88b29..9e0981c 100644
--- a/learn/humans/README.md
+++ b/learn/humans/README.md
@@ -289,6 +289,13 @@ explain. I check to see how receptive they are to learning or receiving
critical feedback and if it aligns with the way they described they like to
receive feedback.
+There are several defects in the code that they are given. This is deliberate to
+see if they are willing to challenge the status quo and to see how well they
+trust their intuition. So far most candidate leave code comments to indicate
+that they think something is wrong but they chose not to do anything about it.
+I would love to see a candidate open an issue to describe what they see wrong so
+that it can be tracked and followed up on later.
+
I try to reserve 5-10 minutes at the end for them to ask questions and I ask
them to give me feedback.