Handling complex code base, maybe with team collaboration.Wrapping implementation details into code blocks: function decomposition, OOP, modules, complex data structures. Making small game projects which most likely fail, but prepare student for next stage (you can't learn to solve a problem if you don't understand what the problem is). Learn mentally to follow debugger cursor.Īt that stage people implement some sort/search algorithms.Valuables, conditional statements, getting input, printing to output. Some very basic language syntax and concepts.Plus Gitlab has very good integration with VSC, you can easily import a repository directly to it and handle all your git stuff right there.Ī more basic editor is just fine for beginning, but IME it’s not too long past print(“Hello World”) that all of these other features come in handy, and VSC is both powerful when you’re ready for it and pretty easy to figure out when you aren’t. Since I’m often also doing Ansible and Gitlab-CI, or reviewing json dumps, or need to make sure json is well properly written to paste into another application, VSC serves all these purposes very well. What I like about VScode is that it can handle lots of other languages. I still keep npp for that purpose on my windows machine, and my Linux machines are almost always vim or gedit depending on what I’m doing.
I wouldn’t use it for every day text editing. It was more bloated and difficult to get working on my system. Eh, I used anaconda at first and I didn’t like it.
0 kommentar(er)
