Interview before drafting, not when it seems needed#1403
Merged
Conversation
"If needed" asks whether there is a gap, and that judgment gets made from inside the gap, so it always comes back no. Worse, a large pile of verified facts reads as coverage. It is depth on whatever you already knew to look for. The last post never got an interview. What one would have surfaced: that lori had not been released, that ponyup's Windows PATH behavior raises an open question worth asking readers about, and that Windows support rather than PATH support is when that behavior started. The PATH question became the strongest item in the post and existed nowhere but the author's head. The suggested questions are the ones that work without having spotted anything: what have you been working on, what matters most, what is coming, what has actually shipped.
ponylang-main
added
the
discuss during sync
ponylang-main
removed
the
discuss during sync
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
"If needed" asks whether there's a gap, and that judgment gets made from inside the gap, so it always comes back no. Worse, a large pile of verified facts reads as coverage when it's only depth on whatever you already knew to look for.
The last post never got an interview, and the skill said to run one "if needed." What one would have surfaced: that lori hadn't been released, that ponyup's Windows PATH behavior raises an open question worth putting to readers, and that Windows support rather than PATH support is when that behavior started. The PATH question became the strongest item in the post and existed nowhere except the author's head.
Step 6 becomes "Interview the author, then verify" and says to interview before drafting, always. The suggested questions are chosen because none of them require having spotted something first: what have you been working on that isn't in the issue, what matters most this week, what's coming, and what has actually shipped versus what's still on a branch.
The second "if needed" in the don't-fabricate section now points at step 6 instead of leaving the decision open.