Yeah. I can think of several people who use LLMs to write business processes/procedures. Like writing logical code, they are writing the rules and descriptions _of work_. It’s the killer app for small businesses and I guess for managers in corporate firms.
Huh. I’ve never read a code project page on GitHub that sounded like a Keynote speech at a developer conference. Not sure what to think about that as a reflection of the project’s design, use and governance. Other than I’m supposed to conquer the world using this software?
I’m not familiar with ontology software. So I will continue to read this and see if I can learn how I might grow my handwritten taxonomy into something actionable for my wiki and prompt repo.
If you only want "grow my handwritten taxonomy into something actionable for my wiki and prompt repo" than Sutra-OS is not the right tool. I would use Logseq for such a thing. If you feel the limits of stuff like Logseq in the future you should explore Sutra-OS. It extends the idea of a knowledge-graph to actionable-knowledge-graph.
I manage my own DNS record at zoneedit (set it and forget it). What’s something else (tricky, instructive, whatever) about running your own DNS that I don’t experience?
It's not tricky. The problems are entirely due to one or more of
* Not understanding what DNS is (eventual consistency etc.)
* Round peg square hole problem ("oh we rely on the record updating instantly")
* Using a Microsoft products to serve DNS
I’m “living the dream” in outer NYC, and I own a motorcycle for funzies. Best of both worlds. I do not have the blessing of children, so I expect that would change everything.
The public outage map is primarily a marketing page, because customers receive deeper insights in-product. Given that most people discuss outages live/up-to-the-minute on Twitter, that is why its where we default to sharing.
HA! One size fits all. If that's the community this website is targeted towards, then have at it. Elsewhere in the world of sharing, users get to choose the platform where they're at.
reply