We'll get commercial nuclear fusion earlier.

Authored by Mark Seemann, a software architect and consultant, this blog focuses on software design, object-oriented programming, and functional programming principles. Readers can explore articles and discussions on topics such as dependency injection, domain-driven design, and test-driven development. Additionally, they can learn about architectural patterns, design patterns, and best practices for building robust, maintainable software systems.

ploeh blog

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."

Git integration is ten years away

Completely agree. Now a days, developer knows only how to pull and push. That too via IDE and struggles with command line. Everyone should learn git commands and don’t limit them self to particular IDE only.

Don’t forget tools like Lazygit that bridge this gap a bit

This is why I use GitKraken. Not integrated, but more than capable. And it’s pretty.

We need something better than git. It’s an awful terrible interface

Never saw a “improved Git integration” to work a rebase, reflog, bisect, cherry-pick, stacked branches…