I can't count how many times this has saved the day. VS Code comes with no UI for git, but these two plugins are really helpful to fill some of the features. I'm not going to explain how they work, since they have a really good description in their respective marketplace pages. This is my setup to boost your productivity working with VS Code if you're used to working with WebStorm. The truth is that I wasn't using the right setup for me.Īt Codegram most of the team use VS Code, on twitter there are many people that I follow (and that I look up to) that use it too, so the real question is, why not? I had given several tries in the past, why not another one? The migration setup But every time I tried to use VS Code in my job, I ended up frustrated, but it was because I wasn't feeling productive. I just used VS Code for personal projects mostly to try something new, both the IDE and the project itself. Since then, I've been working mostly with IntelliJ for the backend stuff and WebStorm for the frontend. When I began to work as a developer, my IDE was Eclipse until one awesome day I discovered the JetBrains suite and it was love at first sight. You can do the exact same thing with many different tools, but with your favourite one you just do it faster and better, it boosts your productivity. And this is perfectly normal, you feel more productive and everything feels really easy to do. Jokes aside, it's a fact that when we get used to working with a specific tool, in the end we all tend to fall in love with it. But after all this time and all the experience behind us, I think we're both more mature now and it's the perfect time for this relationship to finally work. We've broken up and got back together so many times I can't even tell. My story with Visual Studio Code (aka VS Code and vscode) hasn't been the typical love story but more of a toxic relationship.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |