Unverified50% confidenceOpinionExact time
The developer believes the information most worth bringing back to a new session is 'what was rejected' rather than 'what was decided,' because decisions are usually already reflected in the code, whereas rejected options leave no trace.
1
Sources
50%
Confidence
Long-term
Relevance
11/5/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedTo judge whether an explanation is worth giving, you can ask: is this explanation supplementing necessary context, or is it defending a decision already made? The former is worth writing; the latter can usually be omitted.62% similarUnverifiedFor planning-centric products, users judge whether "the thing got done," which makes it easier than conversation-centric products to form clear willingness to pay and usage habits.62% similarUnverifiedThe design philosophy of general chat products is to give a useful reply as much as possible, attempting inference even when information is incomplete; this is diametrically opposed to the principle of hard refusal required in legal scenarios.62% similarUnverifiedCandidates who think out loud, proactively explore edge cases and optimization directions may receive higher evaluations even if they do not finish writing the code.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1141074API
curl https://kongchang.com/api/v1/knowledge/claims/1141074MCP
get_claim(id=1141074)