yashwantphogat

4 ms·

1. 1.▲
   How do you find early users for an MVP dev tool?

   1 points by yashwantphogat 10mo ago|2 comments
2. 2.▲
   How do you find early users for an MVP dev tool?

   1 points by yashwantphogat 10mo ago|0 comments
3. 3.▲
   by yashwantphogat 10mo ago

   Yes, team size really changes the dynamics. We ran into similar issues when reviews started taking over entire days. I’m building and testing a quieter review approach that only goes deeper when asked, and I’m trying to understand where tha
4. 4.▲
   by yashwantphogat 10mo ago

   That makes sense. A lot of these tools seem to become useful once the extra noise is turned down. I’m actually building and testing a quieter review approach myself and trying to understand what really helps in day-to-day use. would you lik
5. 5.▲
   Who has enjoyed using PR code reviewers? What worked and what didn’t?

   3 points by yashwantphogat 10mo ago|4 comments
6. 6.▲
   by yashwantphogat 10mo ago

   I’ve run into the same wall. The issue is not that AI “can’t code well”, it’s that it’s bad at large, aesthetic refactors unless you constrain the problem very tightly. A few things that have helped me get closer to that 15–20 minute review
7. 7.▲
   by yashwantphogat 10mo ago

   https://mergemonkey.dev/ I’ve been working on a small GitHub app called MergeMonkey. It’s an AI PR reviewer, but intentionally quiet. It runs on new commits, gives a short structured summary (and diagrams for complex change