3 ms·
A big text file, with a heading for each day. In go tasks, troubleshooting attempts, outcomes, links, etc. Then I copy+paste into github issues, commit message
by SimplGy 10y ago
A big text file, with a heading for each day.
In go tasks, troubleshooting attempts, outcomes, links, etc. Then I copy+paste into github issues, commit messages, and wiki articles as needed (part of my deliverables, as @LeifCarrotson puts it).
* No vendor lock-in, no lag, no migration issues.
* Never have duplicate typing because of copy+paste.
* Get a daily history of your work going back into time in a light, portable, ubiquitous format.
* Recover from accidentally hitting the back button while writing a Jira ticket.
* Be able to precisely answer "What did you work on last week" (or last Monday when you logged out of VPN, or anything else)
I have to move the text from my file into the tracking tool(s), and that could be a downside. But I like having a layer of translation there. It lets me select and rephrase snippets that will communicate best in each environment.
Example: https://gist.github.com/SimplGy/a516c54a81fb24f807f9512fed820935 https://gist.github.com/SimplGy/a516c54a81fb24f807f9512fed82...
- jkmcf 10y agoI've been doing this in Evernote for years -- one note for each month, and now I've switched to Quiver which provides a somewhat better experience.
- SimplGy 10y agoQuiver looks really interesting, thanks for sharing. I love that you can export as plain text or markdown. The idea that this would count as "no vendor lock in" to me hinges on exactly how the text export works -- when exported, can I go back to a text-only experience pretty easily, or will I have 1000s of separate text files for each "cell". Sort of a tangent, but hey.