18 points by akhnid 2 days ago
I built Gitmore. Connects via webhooks, tracks commits and PRs, and gives you one dashboard. AI answers questions about activity, sends weekly reports to Slack/email. Connect agent to slack which answers your questions directly from your workspace. https://gitmore.io (free for 1 repo) Anyone else juggling multiple Git platforms?
We have deifinitely used AI just like everyone else, but we are senior 4+ years of experience. Also Gitmore doesn't have the ability to read your code nor execute or write. We only get data from webhooks which are commits/ PR info with no code. Thanks for your Attention.
Pictures on websites have always been either stolen from other sites a long time ago, then stock pictures from Unsplash or Pexels for a while, and now they're AI because that's just the easiest way to get images now. I don't think it's fair to developers to assume that the ones using AI generated images are also vibe-coding the software though. It's not like the ones writing hand-crafted artisanal code are also out with their cameras taking pictures for the website after all.
FWIW I don't disagree with you. I also assume people are vibe-coding things. I just don't think it's fair to assume that means the devs are taking that code and firing it straight up to a production server. They're probably fixing the problems and making it better. I know I do that in my code (most of the time.)
From the FAQ:
Yes, many teams use Gitmore to eliminate or reduce daily standups. Instead of synchronous meetings where developers report what they worked on, Gitmore automatically extracts this information from Git activity.
If your standups are just reports of what code the dev worked on the previous day then that sounds like a great thing to automate away, and Gitmore is likely a great way to do that.
However, that also means your standups are a pointless waste of time, and the solution shouldn't be to automate the pointless waste of time, it should be to improve your standups so they're actually useful. Rather than just saying what code the devs wrote you could use the time to discuss problems that came up, where people are blocked or where they believe they might be blocked in the next couple of days, or just have a bit of a check-in with everyone to see if they're feeling good about their progress. Standups shouldn't be simple progress reports; they should be an opportunity for the team to come up for air and chat with one another. If you're missing that then you're not really a team, you're just a bunch of individual devs working in the same domain. That sucks. The solution isn't removing the meeting with automation.
I've raised this exact point to many team leads throughout my career.
Yet, they unanimously said, they are interested or need to know the progress.
I can't say if thats what they have to report to their managers, but I assume it's something you won't be able to fix from bottom-up.
Wild how many folks vibe code a thing and then claim to have created something that they ask us to plug into critical infrastructure with the ability to read, write, and execute.
No thanks.