A Year Into Remote Work, Developer Tools Are Having a Moment

Roughly a year ago, most engineering teams got sent home with a laptop and a Slack login and told to figure it out. We’re now far enough into that experiment to look at the numbers, and GitHub’s 2020 Octoverse report gives a decent snapshot of what actually happened to the way people build software.

The headline figures are big on their own: over 56 million developers on the platform, and more than 60 million new repositories created in a single year. That’s not a subtle bump — it’s the kind of growth curve you’d expect when a huge chunk of the world’s engineering workforce suddenly has no choice but to do everything through a screen. Hallway conversations, whiteboard sessions, tapping a teammate on the shoulder to ask “wait, why did you structure it this way” — all of that either disappeared or got pushed into tools that leave a written trail. And a written trail is exactly what Git-based tooling is built for.

That’s probably why Git-centric tools climbed so noticeably in developer-tool rankings this year. GitKraken and GitHub itself both moved up, which tracks with what a lot of us have felt anecdotally: when you can’t just ask someone what’s going on with a branch, you lean harder on commit history, PR descriptions, and visual diff tools to reconstruct context. A messy commit log used to be a minor annoyance you’d clean up before code review. Now it’s often the only record of what happened and why, especially across time zones where the person who wrote the code won’t be online for another eight hours.

The PyCharm comeback is a small tell

One detail in the report that’s easy to skim past: PyCharm jumped back into the top 20 most-used IDEs after being absent from the list in 2018 and 2019. IDE popularity doesn’t usually swing much year to year — people pick an editor and stay loyal out of sheer inertia. A re-entry like that suggests something changed in who’s writing Python and how, not just a preference shift among existing users. Data science and backend teams scaling up remote-friendly tooling, more scripting and automation work as teams try to paper over the cracks in their newly distributed workflows — take your pick, but it’s a signal worth watching rather than a blip.

None of this should be surprising if you’ve lived through the last year yourself. The tools that win in a remote-first world are the ones that make asynchronous work legible: clear diffs, discoverable history, review flows that don’t require live conversation to make sense. It’s a bit of an accidental stress test for the whole dev-tools category, and so far the Git-based ecosystem seems to be absorbing the load well.

The open question is whether any of this reshuffling sticks once offices reopen in whatever form they eventually take. My bet is that a lot of it does. Once a team gets used to writing things down instead of saying them out loud, it’s hard to go back to depending on tribal knowledge and hallway debugging. Async-friendly habits, once installed, tend to be sticky — even for teams that get their desks back.