HackerTrans
TopNewTrendsCommentsPastAskShowJobs

dylandevelops

no profile record

Submissions

Show HN: tmpo – CLI time tracker with automatic project detection

github.com
2 points·by dylandevelops·4 mesi fa·2 comments

Show HN: tmpo – Local-first CLI time tracker with automatic project detection

github.com
2 points·by dylandevelops·5 mesi fa·0 comments

Show HN: tmpo – CLI time tracker with Git integration and local-first storage

github.com
2 points·by dylandevelops·6 mesi fa·0 comments

Show HN: tmpo – Minimal CLI time tracker with auto-detection for developers

github.com
1 points·by dylandevelops·7 mesi fa·2 comments

comments

dylandevelops
·mese scorso·discuss
I agree with you. The more I vibe code, the less interested I feel in what I'm building. Working with models that force me to think, especially with personal projects, helps me stay engaged and enjoy what I am doing more.
dylandevelops
·mese scorso·discuss
I agree with you here. Unfortunately, this tends to be the case, with smaller developers paying the price.
dylandevelops
·4 mesi fa·discuss
Anything to replace my Jira dependency!! You are speaking my language
dylandevelops
·6 mesi fa·discuss
Love using GitHub for managing everything. I can create issues of features and bugs and work through completing them in each pull request. I have also recently created my own tool called tmpo, which I use to log my time when working on projects that require billing. Trying to create my own custom tools to speed up my workflow as much as I can.
dylandevelops
·7 mesi fa·discuss
Thank you!

I'm thrilled that the Unix-y approach resonates with you, as that is exactly what I am aiming for!

And yes, you have hit the main tradeoff that I have and am currently struggling with. The auto-detection works great for "I'm in X project, working on X," but it doesn't work well for the exact cases you mentioned.

Right now, this is how I handle these types of scenarios:

1. Context switches in the same repo: I use the description field to differentiate: `tmpo start "Refactoring auth module"` `tmpo start "Fixing CSS bugs"`

    This has the same project name but with different descriptions. When you export for invoicing or just personal statistics, you can see this breakdown.
2. "Non-directory work" (meetings, research, etc): I use `tmpo manual` to create entries after the fact. `tmpo manual` (opens interactive prompt for project/time/description)

    Or I just run `tmpo start "Team standup"` from wherever I am and let it tag to whatever directory I'm in. This is obviously a bit janky.
To be honest, I am still working on solving this problem. I optimized for what I think is most "solo dev working in project directories" because that is my workflow; however, I'd love to get more feedback and contributors to help make it work for others!

A feature I am also working on currently is a category/phase system that can significantly improve tagging time entries.

What is your current workflow? Do you switch contexts within the same repo often, or is the non-directory work the bigger pain point?