Did you ever feel like Visual Studio is rebuilding projects every single time, even when there were no changes to the code?
We can build, change nothing, build again and there we go… VS is starting a build instead of saying all my projects are up to date.
Also, there’s that nagging feeling that even when we do change something, VS is building way more projects that it needs.
Like most things I do in life, frustration led me to look further into this matter.
After working for the last three years with TFS’s classic source control TFVC, I recently moved to a new company and with that, to Git.
Before working with Git, I loved working with TFVC. I thought it was great and pretty much the most I can expect from a source control.
Git however changed the way I work with source control and even the way I think about source control.
This post is a small taste of what Git does and how my workflow changed accordingly. It is not a Git tutorial, but rather my impressions from it. I do link at the end to some additional resources.