
When he calls me for advice, I ask him if he's been interviewing. He's a fifty-something guy, worried his chances and not too proud to take a step back. Increase in health insurance benefits co pay.Īpparently, he was the 3rd person on his team to get this offer.one of them accepted. He has twins who just started college in the fall and the financial stress was keeping him up at night. He had not updated his resume in 11 years, lol.Ī Senior Product Engineer by trade, he and almost his entire department were let go.Ĩ weeks TO THE DAY, he got a call from his old boss. My favorite thing about VS Code is the ecosystem of extensions, and they don’t fall short in the Git realm.Laid off from his job of 11 years back in October. It also, let’s you compare code from different branches, view remote branches, and so much more! Wrap Up

This one easily replaces several of the ones we have already mentioned.

I leave all of my code projects in a code folder. You can specify which directory to look in for Git projects. Git Project ManagerĮver wanted to easily open up other projects in VS Code? Well, this extension will let you do just that with Git projects. It will show you at a glance who was the last person to change a file. Git BlameĮveryone is looking for someone to blame when something goes wrong (not really, but still), and Git Blame will provide you that information. You’ll have access to commit information, view diffs, etc. This extension lets you quickly investigate the history of a line or file.

The last one is powerful enough to replace them all! Git History Let’s take a look at the top Visual Studio Code extensions for Git and Github! Although VS Code has some great built-in functionality for Git, by finding the right Visual Studio Code extensions, you can power up your Git workflow right inside of your editor.
