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).
So … it is a tool to automate time fraud?
Make sure to put this front and center on your CV
Hey, thanks for the comment. I get that it might be used for something shady, but that’s not the intention. The primary goal is to clean up raw time-tracking data into a format that’s easy to present to clients or supervisors, especially for contexts when small gaps or irregularities should be absent.
I imagine most professionals aren’t expected to account for every single minute of their workday. For example, if you’re switching tasks or taking short breaks. It’s more about reporting general productivity or overall progression of tasks, not trying to inflate hours.
Anyone aiming for ‘time fraud’ could probably find easier methods. My focus is to make life easier for people who already track their work but want cleaner, more digestible reports.
Appreciate the feedback though, helps me make sure the use case is clear! :)
Pretending the most important use of bit torrent is Linux ISO’s is the kind of cya that people giggle at.
If a candidate I am interviewing has a tool to change their reported hours to me or clients on their public GitHub? That person is radioactive no matter how many times they say “but don’t do anything naughty wink wink”
Am I missing something? It looks like OP has to track their time and send it to a client or superior. What is wrong with making a tool to track your time over using excel? I’m sure if they wanted it through a specific end point they would have provided that.
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.
I don’t get it.
Where’s Saddam?
I’ll head back to linuxmemes now.
“FOSS” here doesn’t mean hosted exclusively on proprietary Microsoft GitHub, right?
Yes, I’ll host the source code on GitHub. I could consider mirroring it on Sourcehut if there’s enough interest, but I prefer the PR and Issues workflow on GitHub for collaboration. Plus, more people tend to have GitHub accounts than GitLab or Sourcehut, which makes it easier for contributors.
I get the concern about Microsoft, and while I’m not a fan of the company, GitHub has advantages that are hard to beat, especially for community reach. As for OpenAI potentially using the code, personally I don’t mind if my own code gets used for AI training.
I’ll be using an MIT license, in case you’re curious. Everyone is free to mirror it anywhere.
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…?