Git worktrees: stop stashing and work on two branches at once
Worktrees let you check out several branches of the same repository side by side. They're built into git and remarkably underused.
Topic
Editors, CLIs, version control and developer productivity.
Worktrees let you check out several branches of the same repository side by side. They're built into git and remarkably underused.
Good reviews catch bugs and spread knowledge without bruising anyone. Small habits on both sides of the pull request make the process faster and kinder.
Slow CI quietly taxes every pull request. Measure first, then cache, parallelize and stop doing work that doesn't matter.
A handful of fast, focused command-line tools can replace minutes of clicking every day. Here's a starter kit and how the pieces combine.
A commit message is a note to whoever runs git blame next year. A few conventions make history searchable and debugging faster.
Saying "we need to refactor" rarely wins a planning meeting. Framing debt in terms of risk, speed and cost does.
Whether to keep all your code in one repository or many is mostly a question of tooling and team structure. Neither is free.
Understanding how your tools are funded helps you predict their future. A field guide to the common business models behind developer products.
Random changes and hopeful restarts waste hours. A scientific approach — reproduce, hypothesize, test, narrow — finds bugs faster.