From 1626c43477562a5465567ac673a8fbf1a46c6d27 Mon Sep 17 00:00:00 2001 From: Roman Galochkin Date: Fri, 13 Sep 2019 13:03:16 +0300 Subject: [PATCH] Update best-practices-writing-questions.md --- best-practices-writing-questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/best-practices-writing-questions.md b/best-practices-writing-questions.md index 505880b..bc64527 100644 --- a/best-practices-writing-questions.md +++ b/best-practices-writing-questions.md @@ -28,7 +28,7 @@ Better\(alternative\): _**"In Jan 2025, I will personally estimate the benefit o There are subtle ways in which your question can break even if you get the above right. -For example, measuring the productivity of your team in terms of number of lines of code written written will fail to capture things like code readability and performance, which might be what you really care about. +For example, measuring the productivity of your team in terms of number of lines of code written will fail to capture things like code readability and performance, which might be what you really care about. Just because a question measures _something_ does not mean that it measures _what you care about_.