Make lists of what's in your fridge, when it expires, what you want to cook for the week, what's missing for that and put it on your shopping list of you need it.

A Timewarrior report script for calculating billable hours. - GitHub - trev-dev/timew-billable: A Timewarrior report script for calculating billable hours.

Some utility functions for timewarrior.

Honestly, I would rather like to see them in timewarrior itself than a standalone script, but they are very useful, providing some command aliases, adding a simple duration syntax, and most importantly allowing to 'restart' a task (you pressed start but did not really yet, just restart at the time you actually start working), or 'restore' (you pressed stop but then continued working on a task, restore is 'continue' which fills the gap in between).

Allows you to add a timewarrior subcommand which displays a nice histogram of past days and a the amount of time you have been working (in general or on something if you filter it).

Works like a normal timewarrior command. Needs some extra dependencies unfortunately.

A very simple full-text search tool for plaintext files.
Can support multiple indexes, uses established search db library, is set up with a single config file.

An interesting approach using sql database to store tasks and retrieve them with all kinds of tools

Assist in organizing your piles of documents, resulting from scanners, e-mails and other sources with miminal effort. - eikek/docspell

Mirrors paperless, but comes with more features regarding ocr (NLP, a learning engine, auto-tagging etc), saves the originals and the pdf versions, can send e-mail, has a much more advanced web interface -- but also consumes more resources.

'Simple' kanboard software - just boards and cards, with a few nice workflow features like highlighting a column that fills up too much.

Can I just say as a neuroscientist this is not your fault. Basically we think we have control over what we do but this is an illusion. For example you want to work on your project but you never do. So then you feel shame/guilt etc which only makes you more unproductive.

The solution to this is that the mind behaves more like a computer than we think. If you know how to properly interact with it you can make it do whatever you want. Now there is a long list of behavioural psychology focused on productivity but I will start you of with one thing.

Right now create a list it can be on your computer a website like trello.com or on paper it doesn't matter. On it write 6 Things that you can accomplish very quickly in relation to your project.

for example the list could be this.

make a project directory for my project.
download the dataset needed
install required tools for project
write first variable
write first function
Make the first graph
Set the commitment to do just one of these things per day, you don't have to do anymore.

Try adding new goals to your list as you complete old ones.

the goals should be easy to achieve 1 minute - 30 minutes for each.

Pretty soon you will be doing more than just one task.

This method efficiently uses your brains reward system. Doing small clearly defined tasks with low commitment is easy and generally fun to do.

Doing a large complicated project with no clear approach is not fun to do.

There are tonnes of efficiency hacks and every person is different. Good luck.

reddit permalink

Tag your time, get the insight. traggo alternative, pretty similar but not based on key:value pairs #tags instead.
More mature interface and reporting functionality, less extensive dashboarding possibilities.

Funny little website which, while taking itself not too seriously, contains some good advice.

7 principles of getting stuff done - following something similar to the pareto principle, deep-work ideas, and so on.

Using pipe2 functionality, could presumably be adapted for newsboat, aerc, etc.

Simple sci-hub batch downloader, written in bash. Has to be adapted to use-cases a little (since hard-coded variables for page url and doi input file)

Other scihub downloaders:

• Sci-Hub - did not work for me last time I tried it, presumably had a missing dependency, or written for outdated python version
• scihub.py - not tested yet, but seems ambitious in that it gets the newest url, checks for captchas, and is pretty flexible in input dois

This is a small hack providing relative recurring tasks with due date some period after completing the current task. Taskwarrior will not learn such a feature before "the Great Recurrence rewrite", which has already been delayed for many years, so this had to be dealt with.

An open source project management tool with Kanban boards.

Replaces Trello (or Nextcloud deck) out of the box, wants to do much more in the future. Perhaps not necessary right now, but might be a good candidate for web integration of e.g. taskwarrior projects in the future.

script to implement GTD workflow better with taskwarrior

• Reminder to do a mini mind sweep, making sure there are no free-floating things
• Project review, where it dumps the pending tasks of each project one by one, and prompts to make any updates (record new tasks, mark tasks done, etc) in another shell
• +next review, where it prompts me to select exactly one +next task for projects that have not exactly one +next task (this is a personal preference)
• Reminder to process e-mail, turn into Taskwarrior items as appropriate in another shell
• Reminder to check last two weeks and next two weeks in calendars, turn into Taskwarrior items as appropriate in another shell
• Dumps my +someday tasks for review
• Dumps my +in tasks, bugs me until they're all gone (by processing them in another shell)
• Runs task sync

Contexts work wonderful for task segregation.
Link contains a simple demonstration of filtering through contexts,
as well as a script with which tags get automatically applied depending on the context one is in (though, does that make sense? I might think of a +Personal task to be done while in my +Work context)

"For your purpose, I would recommend to use contexts based on projects. I use that approach as well and works well with subprojects. Add to your taskrc: context.home: project.hasnt:work context.work: project:work You can switch between contexts: task context work task context home Or completely unset the context to see all tasks independent of the project task context none More about context in the docs For your Jira tickets I would add them to a subproject work.jira so you can filter them by issuing: task project:work.jira Eventually you could just use tags within your project so you can filter them with: task +jira Or a combination of project + tags"

+Tag -> broad life section
project: -> actual project with beginning and end (can be in life section)
+tag -> context of task (where, with whom, etc see GTD)

Good idea for task hierarchy organization in tw:
"I mostly stick with tags, tasks, and subtasks for the structure, with priorities for informal now/soon/eventually scheduling.

Still working out how best to describe broader goals and domains.

Top-level projects kind of work (I have "Site" and "Work" as top-level projects with subprojects for specific projects or narrower domains), but there can be overlap. There's also the "Work is never done" aspect of using top-level projects as domains. It plays hell with your project statistics and keeps that endorphin rush of completion forever out of reach.

I experimented with a UDA for domains. It cluttered things up and was just reinventing tags, poorly.

Current experiment, started about 15 seconds ago: since tags are case-sensitive, use CamelCase to indicate domain: +Work or +Site for example. We'll see how that works out!

And potentially useful tip: tasksh includes a nifty "review" feature for that weekly triage."

Quick explanation of traggo's authorization scheme for interacting with the graphql. Does not seem to be documented anywhere else.