I built Snippet: an auto-updating truth layer for your organization's knowledge.
Show HN: Yikes imagine trusting Google's documentation
usesnippet.app
Show HN: Yikes imagine trusting Google's documentation
1–10 of 20 posts
Re: Show HN: Yikes imagine trusting Google's documentation
#2Thisis really good. I wonder if these "truths" propagate anywhere or not.
Re: Show HN: Yikes imagine trusting Google's documentation
#3Thisis really good. I wonder if these "truths" propagate anywhere or not.
thanks! yes, we enable auto updating documentation, automatic conflict resolution, and accurate search indexing.
Re: Show HN: Yikes imagine trusting Google's documentation
#4Makes sense now why integrations sometimes break unexpectedly. Conflicting info in official docs is a real problem
Re: Show HN: Yikes imagine trusting Google's documentation
#5Makes sense now why integrations sometimes break unexpectedly. Conflicting info in official docs is a real problem
have you seen a similar situation before?
Re: Show HN: Yikes imagine trusting Google's documentation
#6Makes sense now why integrations sometimes break unexpectedly. Conflicting info in official docs is a real problem
have you seen a similar situation before?
Seen it a lot in enterprise environments. Teams maintain parallel Confluence spaces and internal API docs. They drift constantly. The newer page is correct, but search still surfaces the old one first
Re: Show HN: Yikes imagine trusting Google's documentation
#7[dead]
Re: Show HN: Yikes imagine trusting Google's documentation
#8Love the concept. Just curious if and how you guys determine which source is correct in case of a conflict
Re: Show HN: Yikes imagine trusting Google's documentation
#9Love the concept. Just curious if and how you guys determine which source is correct in case of a conflict
We do! An org can define precedence rules, but the engine looks at things like recency, authority, majority voting etc. We also flag criticality to raise manual reviews when needed.
Re: Show HN: Yikes imagine trusting Google's documentation
#10This definitely solves a good problem.
Company don’t keep generally good confluence docs and documentation.
Somehow if there is common source of truth it helps to entire org in a company.
But I was wandering if it will be helpful or not for external world because I feel companies usually double check any information before releasing it publicly ..especially related to code base.(Just a thought).