Can Y.’s Post

GitHub is on pace for 14 billion (!) commits this year. Up from one billion in 2025. GitHub's COO, Kyle Daigle, told The Information the platform now sees two hundred and seventy-five million commits a week and is hitting infrastructure limits. Claude Code alone is up twenty-five times in six months. I have been trying to find a historical comparison. Mass manufacturing is the closest I got, because that handed production to machines too. But quality control was easier there and involved statistical sampling on identical units. Code is not identical and every commit is bespoke. The obvious question is whether quality is keeping up? The less obvious one is whether anyone is even checking. My guess is most are not. Fourteen billion commits need fourteen billion answers to the same question. Did this produce any value?

So GitHub now lets orgs disable commit comments. I can already hear the collective sigh of relief from maintainers drowning in long-dead discussions on ancient lines of code. Or maybe a collective groan from those who loved the context? Either way, a powerful new admin lever. What's your take on this cleanup? #GitHub #DevOps

🔥 Most developers use GitHub every day but only know 20% of what it can do. Here are 10 GitHub tricks that'll make you faster, smarter, and honestly — kind of look like a wizard to your teammates. 😎 One keypress to open VS Code in your browser. URL hacks to download repos instantly. AI-powered repo reading. It's all in the new post on hamidrazadev.com 👇 Read it, save it, and send it to that one dev friend who needs it. #github #webdev #programminglife #devtips #codenewbie #100daysofcode #hamidrazadev

Most people grind leetcode wrong they pick random problems, get stuck, burn out & quit this github repo fixes that it has everything: ▫️15 patterns that cover 80% of problems ▫️ curated problem lists

Typed “guthib” instead of GitHub today… and landed somewhere I definitely didn’t expect. 😄 It’s funny how in tech, even a single misplaced letter can completely change the outcome—whether it’s a search, a command, or a line of code. Moments like these are small, but they reinforce an important habit: being mindful of the details. Because in our field, precision isn’t optional—it’s everything. Sometimes the best reminders don’t come from big failures, but from tiny slips like this. Back to typing carefully… one character at a time. #DeveloperLife #CodingLessons #AttentionToDetail #TechJourney #GitHub

How much time is spent just setting up development environments? GitHub Codespaces seems like a useful way to cut down some of that friction. A few clear advantages: * less time spent on local setup * templates and preconfigured environments can keep things consistent * cloud-based so it's easily accessible Interesting tool to know.

GitHub Rejected My Push — Here’s What I Learned Last week I ran into a frustrating issue while pushing my Reliant Carriers trucker logistics project to GitHub. I kept getting an error saying: “File exceeds GitHub's 100MB limit” After digging deeper, I realized the problem: I had accidentally committed my virtual environment (myenv/), which included a large file (~184MB). Why this is a problem Virtual environments contain installed dependencies and system-specific files. They are not meant to be tracked in version control and can quickly exceed GitHub’s file size limits. What I did to fix it Since the large file was already in Git history, simply deleting it wasn’t enough. I resolved it by: Removing the Git history (clean reset) Creating a .gitignore file to exclude myenv/ Reinitializing the repository Pushing a clean version to GitHub (force push - because I'm working alone,no branches.) Key lesson: Your repository should only contain your code — not your environment. For Python projects, always exclude: venv/ or myenv/ __pycache__/ And use a requirements.txt file to manage dependencies instead. This was a small challenge, but a valuable reminder of how Git actually tracks history — not just files. #SoftwareEngineering #Git #LearnSomethingNew #DevJourney

I pushed .env files to GitHub. Quick fix: delete .gitignore commit Done? That’s where most of us stop. I almost did too. But this time, I paused. Because earlier, I had gone deeper into Git. So I asked: “What about the history?” And there it was. Those files weren’t gone. Just hidden—in commits. Public. Recoverable. So I fixed the real problem: rewriting history locally + remotely. If I hadn’t learned that earlier? I would’ve confidently shipped a broken fix. This is the Dunning-Kruger Effect in action: • Enough knowledge to act • Not enough to question Doing it often makes you fast. Understanding it makes you right.

Apparently GitHub silently reverted 2,804 Merged Pull Requests last week due to a bug! Most are arguing over the 'apology'. In my opinion, the more difficult discussion involves what it means for a 'data integrity' bug to be shipped on a platform that holds the canonical state of much of the codebase that runs the Internet. Code Review is one layer of trust. The Platform that stores and merges your code is a separate layer entirely. If the foundation underneath your Engineering Organization can silently rewrite history, no amount of review at your end fixes that. Is your build trust durable to a regression in the platform underneath?

I thought GitHub Actions was just CI/CD. This book proved me wrong. "GitHub Actions in Action" shows you that GitHub Actions is a full automation engine — not just a pipeline tool. It's already used by millions of developers worldwide to automate any kind of manual task in engineering. And the best part? It doesn't just automate GitHub — it can automate the entire GitHub universe. If you've been sleeping on GitHub Actions, this book will wake you up. Highly recommended for anyone who wants to go deeper with GitHub and rethink how much they're spending on external tools. #github #cicd #distribution #softwareengineering