This article won’t walk through perfectly restoring your entire machine to the state it was before the incident, that’s beyond the scope of my talk. Apparently, I must block this out of my memory every time I have to go through it, because let’s be honest, it’s just a big pain. In that moment, I am reminded of just how painful set up and configuration is. Especially when it comes to my IDE (Visual Studio Code) - I have it tweaked and set up just how I like it, and in a blink, it could all be gone. Coffees get spilled, laptops slip to the floor, OSs get corrupted, and other people can be less conscientious with themselves and their stuff.Īt that point, I have a problem, I have a new or freshly reset laptop devoid of all my personal settings, plugins, random installs and preconfigured tooling that makes development easier and more fun. It’s the install-once-globally-and-then-never-have-to-think-about-it-again mentality.Īnd I know this is a dangerous game to play, because while I’m usually careful with my personal effects, things happen. Some things, like tools I use regularly, I remember, but most things I’ve installed on it, I probably don’t.

I’ve had my current, work-issued MacBook Pro for just under two years, and as you might imagine as a software developer, I’ve installed a lot of stuff on it. VS Code - the best JavaScript IDE available today My Optimum Work Setup & How I Play with Fire

Visual studio code git first time