3 ms·
My read is that this isn't a productivity tool at all. It's a way to capture who to bill for your work (Billable vs. overhead time). "generate and send PDF inv
by rubidium 9y ago
My read is that this isn't a productivity tool at all. It's a way to capture who to bill for your work (Billable vs. overhead time).
"generate and send PDF invoices pre-filled with your coding activity." is in the future roadmap. And the pain of keeping track of billable hours is what drove him to write it to start with.
Keeping track by program used is a nice-to-have, because then someone on the team could notice "hey we spend a lot more time with tool X then makes sense, maybe there's a way to improve that?"
- ballenf 9y agoFeel kind of silly for missing that use case. Could be especially helpful on consulting based teams, for sure. I'm rather consoled by these responses that the expectations for the tool are lower than what I expected. It does one simple thing very well it seems. Some need that data, some don't, but no one here is purporting it to equate with code quality or productivity.
- Domenic_S 9y ago> "generate and send PDF invoices pre-filled with your coding activity." is in the future roadmap. I love the guy's success but man do I hate this idea. I'm billing for more than time in vim. If you're my client and I'm answering an email from you, I'm billing you for that. If we're on the phone, the clock is running. If we're on a Hangout, you're paying. Could you imagine if your employer only paid you for time spent in an editor?
- welder 9y agoThis is solved with good UI, where you see the time you were coding as a starting point then add any non coding time before sending the invoice.