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.
Mainly, this is because I was writing official docs, then took a quick Lemmy break, but my brain stayed “official” hahahahaha that’s all. ‘they’ should absolutely be used in this colloquial context.
Don’t know why you would jump to that conclusion straight away. Mín billable hours and time spent thinking on the problem is a thing. Taking regular 5m breaks (pomodoro technique) also helps with getting things done and so on and people should be paid for it.
I mean, you should technically stop the clock if the wife calls to ask if there’s pasta at home but nobody really cares.
Adding significant amount of hours to a report would not be ethical but adjusting 10% to get paid for time laying in bed thinking about problems is still ethical from my point of view. It’s way more value than most meetings.
Your cultural context way vary.
What someone feels is ethical and what may be legal don’t always match. From a legal point of view in every country I’ve worked at as a contractor, “time laying in bed thinking about problems” isn’t billable time.
As a personal time management solution, I don’t see any issues here. As a billable time report maker, it has the very real potential to get the user into legal turmoil.
Use at your own risk and made damn sure that the laws match your idea of ethical billable hours, is all I’m saying.
This sounds really cool. I have actually made something similar (unpublished and quite hacky though).
I work as a self-employed contractor and must report my times in varying standardised formats, depending on the client or agency I am working with. My input data comes from TimeWarrior (like yours) and I usually just output CSV data so I can copy-paste that into a provided excel template.
Quantizing the data is usually the most essential step as the templates often restrict accuracy. I find it strange that many of the comments here presume this kind of transformation to be fraudulent.
As someone who works atrocius times of their own volition & has to create a clean timesheet every end of the month, this is a great idea -buyt there are too many special rules to consider imo - also I never properly track time (keep forgetting) but reconstruct work times from emails, chats & calendar entries :)
Could have some kind of floating timer window/widget in your bar so you don’t forget
The problem is working on different computers & sometimes switching back and forth between private time and work time. That’d require actual button presses or something to “clock” in/out
Ah I see. At my previous company we developed an in house clock in/out system that I always forgot to use. Never did but I wanted to build a big red button with an Arduino that clocked me in and out with the API and showed a timer
I don’t get it.
Where’s Saddam?
I’ll head back to linuxmemes now.
I just say I worked X hours per day, above my log entries describing what I did that day. Why do they need anything more than that?
Sometimes I work on a larger project that is split up in different sub projects, that were sold separately and are maybe paid by different departments. So I need to at least spilt those up.
Also it’s often easier to follow what exactly was done, when I differentiate more between my tasks and not just put a collective line there - just like small commits are more helpful than one large one.
But maybe I understood you wrong…?
