Best of Git — December 2025
- 1
- 2
CodeHead·21w
The Framework To Becoming A Good Programmer
Becoming a good programmer requires a systematic framework: understand problems thoroughly before coding, design solutions through decomposition, write readable code with clear naming and small functions, debug methodically using hypothesis testing, build progressively complex projects, use version control meaningfully, read production code regularly, and seek feedback aggressively. This disciplined approach builds judgment and accelerates learning more effectively than memorizing syntax or switching languages.
- 3
freeCodeCamp·20w
freeCodeCamp's New Relational Databases Certification is Now Live
freeCodeCamp launched a new Relational Databases certification covering Bash scripting, SQL, and Git. The certification includes interactive lessons, workshops, labs, and quizzes across multiple modules, with five required certification projects. Students must pass a 50-question exam using an open-source exam environment that runs on laptops/desktops. The certification is free and verified, with anti-cheating measures including randomized questions, weekly attempt limits, and manual review. Exams are closed-book and timed, with one attempt per week allowed. The certification replaces portions of the previous Full Stack Developer certification.
- 4
Developer's Journey·22w
A month ago, I posted my Obsidian setup, and since then, I’ve rebuilt and refined it a lot — here’s the updated system that’s been keeping my coding + learning organized.
A developer shares their refined Obsidian vault system after a month of iteration, featuring structured folders for projects, clients, education, and logs. The setup includes templates for daily notes, client tracking, and blog posts, with integration into their coding workflow through Git and VSCode. The system consolidates coding, studying, content planning, and progress tracking into a single organized workspace.
- 5
ploeh blog·19w
Git integration is ten years away
Git integration in IDEs like Visual Studio has been under continuous development for over a decade, with "improved Git integration" appearing in release notes since 2013. Rather than waiting for perfect IDE integration, developers should invest a few hours learning Git fundamentals through the command line. This tactical approach provides immediate productivity without dependency on IDE features that may perpetually remain "in development."
- 6
Google for Developers·22w
3 skills every early-career engineer needs
Early-career software engineers should focus on three fundamental skills: writing clean, maintainable code with meaningful names and simple logic; developing a quality mindset through comprehensive testing that prevents regressions and enables confident refactoring; and mastering essential tools like version control, debugging techniques, documentation practices, and communication skills. These foundational practices create long-term career success more effectively than chasing the latest frameworks.
- 7
Programming Digest·22w
No code reviews by default
Raycast's engineering team operates without mandatory code reviews, allowing engineers to push directly to the main branch and request reviews only when needed. This trust-based approach emerged from their early startup days and scaled with their distributed team. They prioritize rapid iteration through daily internal releases, dogfooding changes within 24 hours, and shipping public updates every two weeks. Code reviews are still used selectively for unfamiliar code areas, database migrations, or onboarding new team members. The team relies on post-commit notifications, quick video calls, and continuous integration to maintain quality while avoiding the bottlenecks of traditional pull request workflows.
- 8
YouTube·20w
linus messed up the linux git history (so now there's a new git option)
Git repositories can have multiple root commits, which can cause problems with history traversal, file tracking, and bisection. This became a notable issue when Linus Torvalds accidentally merged an unrelated GitHub-generated README into the Linux kernel, creating a second root commit. The incident led to Git introducing the `--allow-unrelated-histories` flag, which now prevents accidental merges of unrelated histories by default. You can find root commits using `git log --max-parents=0` and should be cautious when merging pull requests that might introduce new roots.
- 9
Viget·20w
Don't Let Vibe Code Become Legacy Code
AI-generated code can quickly become unmaintainable legacy code if not properly managed. Four key practices help prevent this: take ownership by writing code yourself or defining tests/interfaces manually, review your own pull requests thoroughly, write meaningful commit messages that explain the 'why' behind changes, and use AGENTS.md to centralize AI tooling rules across your team. These traditional software engineering best practices remain essential even when using AI coding assistants like Cursor or Claude Code.
- 10
Atlassian·23w
Bitbucket’s new look: user experience and navigation updates coming soon
Bitbucket Cloud is getting a visual redesign and navigation overhaul in early 2026, aligning with Atlassian's unified design system. The update includes modernized navigation for faster access to repositories, pull requests, and pipelines, along with improved typography, color system, iconography, and components for better readability and accessibility. Icons and components will roll out progressively over the coming weeks, with the full navigation update launching early next year.
- 11
Reid Burke·19w
steipete/RepoBar: Show status of GitHub Repos right in your menu bar and terminal: CI, Issues, Pull Requests, Latest Release.
RepoBar is a macOS menu bar application that provides a dashboard for GitHub repositories without opening a browser. It displays CI status, releases, pull requests, issues, and activity metrics. The tool includes local Git state monitoring, automatic repository syncing, OAuth authentication via Keychain, and a bundled CLI for terminal access. Installation is available via Homebrew or direct download, with auto-updates through Sparkle.
- 12
Git & GitHub Crash Course for Beginners
A comprehensive 1-hour video course covering Git and GitHub fundamentals, including core commands (add, commit, status, log, reset, restore), branching and merging strategies, handling merge conflicts, remote repository operations (push, pull), advanced workflows with stash and rebase, and collaborative development through pull requests. Designed to build strong foundational knowledge for developers new to version control.
- 13
ForrestKnight·21w
33 Linux Commands EVERY Dev Should Know
A walkthrough of 33 essential Linux command-line tools for developers, including modern alternatives to classic commands. Covers file searching with ripgrep and fd, terminal multiplexing with tmux, Docker management with lazy-docker, Git workflows with lazy-git, network diagnostics, process monitoring, and various productivity tools. Demonstrates practical examples of each command with emphasis on Rust-based modern alternatives that offer better performance and user experience than traditional Unix utilities.
- 14
Windsurf·20w
Windsurf Wave 13: Merry Shipmas
Windsurf Wave 13 introduces parallel agents for concurrent task execution, Git worktrees support, multi-pane Cascade interface, a dedicated terminal, and SWE-1.5 Free tier. These updates enhance the AI-powered coding assistant's capabilities for managing complex development workflows.
- 15
Armin Ronacher·20w
A Year Of Vibes
A reflection on how AI-powered coding tools fundamentally changed software engineering practices in 2025. The author transitioned from traditional coding to working with agentic tools like Claude Code, publishing 36 posts and having extensive conversations about AI. Key challenges emerged around version control systems not capturing AI-generated code context, code review workflows needing redesign for human-AI collaboration, and the difficulty of separating human intent from machine output. The piece explores the anthropomorphization of AI tools, the rise of terminal-based coding agents, and identifies opportunities for innovation in observability, version control, and establishing new social contracts for AI-assisted open source contributions.
- 16
Lobsters·19wPackage managers keep using git as a database, it never works out
Git repositories initially seem ideal for package registries with built-in version control and distributed architecture, but major package managers like Cargo, Homebrew, CocoaPods, and Go modules all eventually abandoned git-based indexes due to performance problems. As registries grow, git's filesystem limitations cause slow clones, expensive delta resolution, and CI bottlenecks. The pattern is consistent: start with git, hit scaling issues around directory limits and cross-platform compatibility, implement workarounds like sharding, then migrate to HTTP-based protocols or CDNs. Git lacks database features like constraints, indexes, and efficient point queries that package registries actually need.
- 17
Milan Jovanović·21w
The New .slnx Solution Format (migration guide)
Microsoft introduced .slnx, a new XML-based solution file format for .NET that replaces the verbose, GUID-heavy .sln format. The new format is human-readable, easier to merge in version control, and aligns with the simplified .csproj format. You can migrate existing solutions using either the .NET CLI command 'dotnet sln migrate' or Visual Studio's 'Save As' feature. The format is supported in Visual Studio 2022 (v17.13+), Visual Studio 2026, Rider, and .NET 9 SDK (9.0.200+). While technically in preview, it's stable and safe for production use, with the primary benefit being dramatically fewer merge conflicts.
