3 ms·
I want an automated work timeline tool. There are things I do that are semantically linked, grouped by timing. For example: I get an issue in Jira "enable
by bloopernova 5y ago
I want an automated work timeline tool. There are things I do that are semantically linked, grouped by timing. For example:
I get an issue in Jira "enable AWS feature for project X".
I search for AWS and Terraform documentation on those subjects.
I edit code on a feature branch named for the Jira issue.
I save links and notes into my Emacs org-roam knowledge base.
I test the new feature.
I submit a PR.
I edit documentation to support the new feature.
I add to the architectural decisions for the team and the project.
I close the Jira ticket.
All those things might happen within an hour or two, or be dragged out longer for bigger features. I want that temporally and semantically linked set of activities to appear on a timeline with links to and from the various tools I use.
Why? The more data the better. Being able to search for "AWS S3 policies" and get information from all the bits my brain "touched" to implement something. This is also something that might help those team members who are less likely to correctly document or record their work.
Now imagine that, but for a team. This is a half-finished idea, born mostly from a desire to link my Firefox bookmarks' tags and the tags in my org-roam knowledgebase.
- barefeg 5y agoI also dream of environments where all the things can interact with each other. Currently there’s a lot of services for almost everything, but little ability of connecting things
- fikama 5y agoAgree this is one of the reasons why I like command line. This and scripting are one of the biggest problems of GUI for me
- waldo2k2 5y ago> I want that temporally and semantically linked set of activities to appear on a timeline with links to and from the various tools I use Sounds like what you want is a repeatable, digital workflow. Using workflow software like Process Street (https://process.st https://process.st) you can build that documentation as part of performing the work itself. You could capture, say, the AWS policies you create and the ARNs they’re associated with in the workflow. You could automate integrations with Jira (or just about anything if you use Zapier) as steps are completed. You can start off simple and build on as you go. Disclaimer: I work for Process Street.