If git status takes four seconds and your git client takes forty to draw the history, it's easy to blame the repository. It's big, it's old, and a few hundred people commit to it. But git has settings for exactly this problem, and most of the big repos I've worked in had never turned any of them on.
This is what I set up on every large clone, and how to tell whether it helped.
Git Revenge is a desktop git client that stays fast on huge repositories. Point it at the Linux kernel's 1.5 million commits and the first rows of the graph are ready in about 415ms. It drives the git you already have installed, with no accounts, cloud features or AI, and it's free under Apache-2.0. It runs on Windows and macOS, with Linux arriving in 0.10.0.
Your video meetings are probably leaking cognitive resources faster than a memory leak in production. What started as a temporary solution to stay connected during 2020 has become a permanent drain on mental bandwidth.
The problem isn't remote work itself — it's how we've implemented virtual collaboration. Let's optimize this system before it crashes your productivity entirely.