TimeFly tracks your coding to stop procrastinating and finish your projects. Built because I kept getting excited about side features and forgetting my goals. See your real coding patterns and ship what matters. Full details on the site.
Show HN: Clean metrics for messy coding habits
1–7 of 7 posts
Re: Show HN: Clean metrics for messy coding habits
#2[deleted]
Re: Show HN: Clean metrics for messy coding habits
#3Carlos here, one half of the TimeFly dev duo.
We're in beta, shipping fast and paying close attention. Found a bug or have a cool idea? Let us know!
Right now, TimeFly shows your top projects, languages, IDEs & devices, activity heatmap, coding session insights, and daily recaps (useful for standups).
Trust me, it's a game changer.
P.S. I'm the guy behind the frontend and design. Go check the UI, it's neat and kind of fun: [https://timefly.dev](https://timefly.dev/)
Re: Show HN: Clean metrics for messy coding habits
#4what's the point? I can name offhand the projects and languages I've been working in for a given day or week. failing that, I can just look through my commits or jira.
your usecase ("I got excited by side features") is easily solved with a basic-ass kanban board. just finish your tickets.
your site also posits to "get rid of standups", but standups aren't generally about the code you wrote. they're about connecting with your team on concepts that are blocking you or others.
sure, it's neat, but is it neat enough for me to want to integrate all this stuff and potentially give you data I don't want to give you? what's in it for me?
Re: Show HN: Clean metrics for messy coding habits
#5what's the point? I can name offhand the projects and languages I've been working in for a given day or week. failing that, I can just look through my commits or jira. your usecase ("I got excited by side features") is easily solved with a basic-ass kanban board. just finish your tickets. your site also posits to "get rid of standups", but standups aren't generally about the code you wrote. they're about connecting w…
Kanban boards and Jira tickets are manual. The point of TimeFly is automating that part, you don’t have to log tasks or go back through commits to reconstruct your week. It gives you a clean, visual timeline of what you actually worked on, without extra input.
We’re also working on features to track progress toward goals and to generate reports if you ever need to justify your time objectively (instead of estimating it by hand) which is something I’d definitely value myself as a client.
It might not be your exact use case, but it still provides value by taking away the overhead of manual tracking while giving you structured insight.
Re: Show HN: Clean metrics for messy coding habits
#6what's the point? I can name offhand the projects and languages I've been working in for a given day or week. failing that, I can just look through my commits or jira. your usecase ("I got excited by side features") is easily solved with a basic-ass kanban board. just finish your tickets. your site also posits to "get rid of standups", but standups aren't generally about the code you wrote. they're about connecting w…
Kanban boards and Jira tickets are manual. The point of TimeFly is automating that part, you don’t have to log tasks or go back through commits to reconstruct your week. It gives you a clean, visual timeline of what you actually worked on, without extra input. We’re also working on features to track progress toward goals and to generate reports if you ever need to justify your time objectively (instead of estimating…
very weird, IMO, to not plan your work but let your work dictate your plan... I don't see how this helps keep you organized when the nature of your issue (getting distracted) comes from a lack of planning / self-editing.
Re: Show HN: Clean metrics for messy coding habits
#7Earlier quoted context omitted.
Kanban boards and Jira tickets are manual. The point of TimeFly is automating that part, you don’t have to log tasks or go back through commits to reconstruct your week. It gives you a clean, visual timeline of what you actually worked on, without extra input. We’re also working on features to track progress toward goals and to generate reports if you ever need to justify your time objectively (instead of estimating…
very weird, IMO, to not plan your work but let your work dictate your plan... I don't see how this helps keep you organized when the nature of your issue (getting distracted) comes from a lack of planning / self-editing.
i'm not talking about not having a plan. I'm talking about not wasting time checking your progress against that plan and having real proof of work to show if needed