@robj3d3: I never understood the hype over counting git commits. “I made 100,000 commits this month!” Okay but did you commit eve…
Summary
The tweet questions the value of counting git commits as a productivity metric, suggesting a need for better alternatives in software development.
View Cached Full Text
Cached at: 09/22/26, 09:44 AM
I never understood the hype over counting git commits.
“I made 100,000 commits this month!”
Okay but did you commit every other line of code, or is that 100,000 features?
We need a better metric for measuring productivity.
Similar Articles
@MTSlive: SITUATION DETECTED: GitHub’s monthly commits have grown from 1.4 billion in April to 2.9 billion in August.
GitHub's monthly commits more than doubled from 1.4 billion in April to 2.9 billion in August, indicating a significant increase in developer activity on the platform.
Why I still hand write my commit messages
The author argues that hand-writing detailed Git commit messages is valuable for explaining the 'why' behind changes, aiding personal understanding and code review, even in the age of AI-generated messages.
Stop Using Conventional Commits
A critique of Conventional Commits arguing that it prioritizes commit type over scope, which misguides contributors and fails to deliver on its promises.
Why don't people use git properly?
An essay exploring why many developers struggle to use git properly, covering common mistakes like panic over merge conflicts, huge commits, and poor branching practices, and examining the root causes.
@danshipper: GitHub has a front-row seat to how code is changing now that everyone—and their army of agents—can ship code. In March …
GitHub COO Kyle Daigle discusses the surge in AI agent-created pull requests (17 million in March) and the projected 14 billion commits this year, emphasizing open-source maintainer control, usage-based pricing over per-seat licensing, and the collapsing developer/non-developer distinction as AI tools enable non-developers to build apps.