Discover and read the best of Twitter Threads about #foo
Most recents (2)
One tweet summary of @RoamResearch.
Type a sentence like:
- Had #meeting with #JohnSmith about #defi
You get:
- a page with all meetings (#meeting)
- a page with all mentions of a person (#JohnSmith)
- a page with all mentions of a concept (#defi)
It indexes your text.
Type a sentence like:
- Had #meeting with #JohnSmith about #defi
You get:
- a page with all meetings (#meeting)
- a page with all mentions of a person (#JohnSmith)
- a page with all mentions of a concept (#defi)
It indexes your text.
Some common questions:
- You can use either #foo or [[foo]] to designate a page
- You can collapse #john and #JohnSmith into one page
- You can autodetect old mentions of #foo
- You can build up tags for people, places, ideas
- You can, in theory, link these tags across repos
- You can use either #foo or [[foo]] to designate a page
- You can collapse #john and #JohnSmith into one page
- You can autodetect old mentions of #foo
- You can build up tags for people, places, ideas
- You can, in theory, link these tags across repos
People often name "bidirectional links" as the core concept behind @roamresearch, but it's more like semantic annotation of text.
Next step would be to make this even more automatic. Ideally: paste in text, get automatic tag recommendations, and then manually approve.
Next step would be to make this even more automatic. Ideally: paste in text, get automatic tag recommendations, and then manually approve.
We built this internally and it is a godsend, particularly as you can then start layering on remediation advice for the developer.
Nobody should have to Google an error your organization fixes 100,000 times a year.
Nobody should have to Google an error your organization fixes 100,000 times a year.
Rough shape of the things you can do:
Your build failed the linter:
foo.rb line #123 Don’t use hashrockets (=>) use {x: “something”}
Consider setting your IDE to lint on save. Instructions here: ...
This look wrong? Correct slack channel to raise in: #foo
Your build failed the linter:
foo.rb line #123 Don’t use hashrockets (=>) use {x: “something”}
Consider setting your IDE to lint on save. Instructions here: ...
This look wrong? Correct slack channel to raise in: #foo
Almost all toolchains assume that software development is a single player game. This is catastrophically wrong.
You should cheat the heck out of your local setup by embedding knowledge of how your organization works: where do questions get asked, what are local expectations, etc
You should cheat the heck out of your local setup by embedding knowledge of how your organization works: where do questions get asked, what are local expectations, etc
