This week I’ve been thinking a lot about how I allocate my time, which has made me ask: why work on answer.cloud?
I’m excited about answer.cloud because it’s a knowledge creation engine.
Today I added a small piece of practical knowledge that can be accessed on any LLM or at Slater.app: I documented why a console.log is not showing up in the browser console: hi.slater/ai
Most businesses have useful knowledge that never gets shared. It stays in someone’s head, buried in a Slack thread, or trapped in a slide deck. That knowledge would help users (and future customers), but it’s hard to publish it in a way that actually becomes discoverable and useful.
answer.cloud helps teams turn internal knowledge into public documentation (and helps you spot what knowledge is missing) so it’s accessible through LLMs like ChatGPT, Gemini, Claude, or your own on-site chat experience.
If this resonates, try answer.cloud and publish something you know this week.
