Do you measure your productivity by the number of your git commits?
If you don't measure it by git commits, how do you measure your productivity?
Sales?
Users?
Revenue?
Lines of code?
Trending on Indie Hackers
If you don't measure it by git commits, how do you measure your productivity?
Sales?
Users?
Revenue?
Lines of code?
I measure my productivity by consistency. To me it doesn't matter if i wrote 5000 LoC and 100 commits in 10 days and then did nothing for the rest of the month.
I believe daily development/sales/study/analysis adds up to a productive day if it happens consistently.
Consistency >>>>>> Intensity
MRR, conversions and am i heading towards to the right direction (gut feel at the moment based on twitter/live chat messages/emails/market)
so MRR is a dollar figure.
Conversions. do you keep track of count or percentage?
Have you measured your gut feel? like some kind of internal NPS score? Or even kept some kind of "win board" of screenshots of people's messages/emails.
Percentage, I guess I also track traffic but that hasn't been the key focus at the moment.
| Have you measured your gut feel? like some kind of internal NPS score? Or even kept some kind of "win board" of screenshots of people's messages/emails.
Nope
Unpopular opinion:
Number of hours
Don't tell me you got more shit done in 4 hours than you would in 10 hours.
I don't believe that at all.
Git commits - push one line of code per commit
Users - Make the product free and users will go up (assuming they want it)
Revenue - Charge less than the marginal cost. Revenue will increase, profit will go negative
Lines of code - Programmers comment everything and use brackets and whitespace everywhere
GitHub Issues - Smaller issues will get completed before larger issues
I'm not saying these things will definitely happen. My point is that you need to be very careful that the measurement doesn't lead to the wrong outcome.
Start with the outcome first, and figure out what matters. Sometimes numbers aren't the best way to measure something.
Imagine your desired outcome is to paint the Mona Lisa. What number would you use to measure that? Number of Mona Lisa's painted? Or number of brush strokes on the canvas? None of these make any sense.
Sometimes the only way to know if you've painted the Mona Lisa is to look at the painting and decide if you like it.
The only thing I am measuring at this point for fabform.io is website traffic. That may change later, but for now I am focused on getting eyeballs on the site.
I measure dev productivity by github issues completed. I create github issue with tags like features/bugs/triaging etc etc. and than i generate weekly report to see where my time is going. Ideally majority of it should go into feature development but that does not happen in sw development so there would be some time going in bug fixing or refactoring so that it is easier to add features without introducing bugs etc. If there is too much time going in bug fixing than its an opportunity to analyze further if something can be optimized or if some course correction is required.