|Think about Loose Coupling|
Humane Tasking Initiative / FlowgencyTMby flowdy (Scribe)
|on Feb 20, 2016 at 13:11 UTC||Need Help??|
There is a plenty of software tools of that kind to be discovered online. Either free or for charge, implemented as a webservice or installed locally, command line or graphical, large enterprise-scale project management or simple todo listers for individual use. Lots and lots of stuff like that.
A couple of years ago I very considered using a tool called taskwarrior. I tested it. Liked the multidimensional concept of urgency. I could not help hesitating. Pondering on it, I finally found out what bugs me in regard to urgency calculation that is relevant for the ranking of my to-dos.
I would have liked to configure an urgency criterion "drift between task progress and passage of time". So urgency is determined, with the respective configured weight, by how much I have already proceeded with the task in relation to the elapsed and the available time.
As I cannot code C++, just have a little command of that language, I started to make a feature request for the taskwarrior devs. Soon then I was stuck because I realized it would not be easily feasible. Two major problems needed to be addressed so such a feature would make sense actually:
In the end, I dropped my idea of writing feature request. There is no use to get frustrated by a reply like "uh, tl;dr, could you make a pull request, thx", this at least would be my reaction when faced with a load of pages for a feature request. Rather, I started my own open-source project in Perl. There are great CPAN modules like Moose, DBIx::Class and Mojolicious, so I was sure it is feasible once I get through the elaboration of the time problem. Computer-aided task and time management aligned to individual biorhythm and job conditions, this was and still is my objective. And I got through it. The time model related code is even fairly covered by tests and it works practically, reduced my work-related distress in my "life" time, I have been testing it in my every-day work for more than a year (service administration, software development with Perl).
Because my mid-of-scale, yet another but the better ;) project is written in Perl, I advertise it here in the PerlMonks community. Learn more, and if you are interested, be welcome to test the online demo installation at my Humane Tasking Initiative site. Or read on, clone or fork my FlowgencyTM code repository at GitHub.
Contributions, questions and comments are welcome. Please understand that the tool must remain far from supporting staff performance monitoring. Technically, it can easily be abused like that, like a kitchen knife can be abused for murder. This is why I envision the software project be embedded in an initiative, and why local usage with full own data souvereignty is focussed in development.
To those who find that concept of time overhead I recommend TaskWarrior instead. Between that project and mine can be found a remarkable number of similarities, no wonder because TaskWarrior is my primary source of inspiration. I guess admittingly that the development of Taskwarrior is more stable than the development of FlowgencyTM (by the way, this is a working title subject to change in the future), because I am the initiator and main developer, the only one as yet, whose full-time job deserves priority.