185
It's almost done (it would take one or two weeks to clean it up for FOSS release). It's a CLI tool. It works great for my use case, but I'm wondering if there's any interest in a tool like this.
Say you have a simple time-tracking tool that tracks what you do daily. The only problem is that there are gaps and whatnot, which might not look nice if you need to send it to someone else. This tool fixes pretty much all of that.
Main format is a JSON with a "description", and either "duration" or a "start"/"end" pair. It supports the Timewarrior format out of the box (CLI Time tracking tool).
Outputting clean reports is one thing, but "normalizing" the time to make it look better, or as though I'm more busy, is something else entirely. I appreciate the effort, but this tool has the very real potential to get a contractor or employee sued for time fraud. I highly recommend against normalization of time data. The contractor either worked a full 30 or s/he didn't. It's black and white. Saying s/he worked for 30 when s/he worked for 25 is a lie, and subject to lawsuits and further legal action.
"they" uses the same number of characters as "s/he" and flows more naturally
I'm not sure why "they" isn't used more often to refer to the unknown. This is what we were taught back home when we learned English.
Sure, sure. But s/he reading this might appreciate the use of special characters to improve his/her password entropy.
Wao. What's with the "edu-indoctrination"?
You will be assimilated
Ok, now I'm freaking out 😱
huh?