Thank you for taking the time to give me this feedback, really appreciate it. I think Devlog has the information needed to help answer these questions, but right now it doesn't do a particularly good job of making that easy.
> I question, if my team had poor/nonexistent PRs in the past, when would I be able to get any use out of it, and would there always be blindspots around code that didn't have a good PR.
This is a great question and the answer is that with poor/nonexistent PRs and documentation, Devlog cannot help you other than by incentivizing you to do a better job so that it can be useful — so not that helpful. I'd love to find a way to make it better in this kind of "cold start" case, that's part of why I appreciate your feedback about other potential uses. Thank you again.
My pleasure! I've got a few more thoughts that came up.
It would be nice to know more about how I would interface with your product. It's not clear if it's a daily report, if it's a text box where I ask "What did Intern #3 work on last week?", if it's a chronological page, or something else.
Do different people get different answers? Would a CEO get a different answer than an engineer if they asked what the devops team worked on? Basically do you offer different levels of granularity for different user profiles.
Love the project and looking forward to watching it grow!
> I question, if my team had poor/nonexistent PRs in the past, when would I be able to get any use out of it, and would there always be blindspots around code that didn't have a good PR.
This is a great question and the answer is that with poor/nonexistent PRs and documentation, Devlog cannot help you other than by incentivizing you to do a better job so that it can be useful — so not that helpful. I'd love to find a way to make it better in this kind of "cold start" case, that's part of why I appreciate your feedback about other potential uses. Thank you again.