![]() I have two primary lists, Someday and Maybe. To be clear, I use Working Copy for the Git side of things and Textastic for the writing. There’s good documentation on how to connect the two of them together so I won’t go into detail on that here. On iOS I use two apps Working Copy and Textastic. I could use the command line, but I usually don’t want to. That said, sometimes I switch up my apps so I also have SourceTree around to handle the Git stuff. As mentioned above, on macOS I use BBEdit, this has Git integration so I can theoretically do everything with that. Now it’s time to get into the nitty-gritty! Let’s start with the apps. You can even do a diff, compare two files side by side so see exactly what was added or removed! Version control, in this case, Git, automatically stores what changed and when. Now, I can make a change to my Someday/Maybe lists from any device, including the web, and just type why I changed it. (That said, the sample to accompany this blog post is on GitHub because I know most people are more familiar with that!) There are quite a few services out there offering these, I chose to use Git and to use GitLab for this. Version Control systems are designed for programming, so you can track who changed what, when, and assuming they wrote a decent commit message to accompany the change, why. These are my preferred text-based file editing apps on macOS and iOS, but alone neither of them really hit the spot - until I decided to take some lessons from the professional side of my life and use Version Control. Next, I did some digging around and stumbled across my old friends BBEdit and Textastic. While Drafts is the right tool for many jobs, it wasn’t quite what I was looking for here. Drafts has versions - which satisfies my want to be able to look back in time, but it lacks explicit change messages connected to these. This is nice and visual but doesn’t offer all the other features I wanted without setting up lots of actions and cobbling things together. I started in Drafts, using the task format. This is a sample task in the format I started with The ability to tweak my system easily without rebuilding it.The ability to track what changed, when, and optionally why.Some interoperability with OmniFocus to make it easy to take things out as well as put things back in, or something I could easily script.There were a few features I knew I wanted from a system: The name comes from Getting Things Done by David Allen, the idea is something is a task or project you want to do, but you can’t work on it right now - so you put it on a list called “Someday/Maybe” to get around to when the time is right.Ī few months ago I turned to Git to try and solve my problem. Some of you may be asking “what is a someday maybe task?”. I’ve tried putting these things in OmniFocus and tagging them, using Trello (which I still use, but for different purposes) and I know there has been more than one paper planner over the years! ![]() Someday and maybe tasks and projects are one of those things where I can never seem to find the perfect system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |