## About me

### My skills

I am a fullstack developer on Linux and macOS, so I work with configs, deploys, containers, web servers and more. My focus is on Python, JavaScript, Git and Bash but you'll find Go, Rust, Ruby and other languages and tools covered here too. 

### My reason for using extensions

The main reason I use extensions is to add support for things I expected to be part of VS Code, like support for certain languages, support for intellisense and convenien like not having to end the opening _and_ closing name of an HTML tag.

I also like tools for productivity. Like being able to manage containers or view files in a remote server, without having to use my terminal.

The extensions I use are focused on making my work and personal projects smoother to manage and to catch things out for me (like linting and syntax checking) to add safety.

But having too many extensions can make your IDE slow to load and hard to navigate. Sometimes they conflict (like multiple Markdown extensions). So I am more selective with extensions, or get rid of them when I don't need them.

I have read an article which said that too much intellisense makes you lazy and ruin your memory in a sense. When you have to make code changes in your terminal or GitHub, you don't know the function name or how to use the arguments because you let the IDE autocomplete it for you. The article recommends keeping on autocomplete (no extensions needed) so that variables and functions already covered in the file can be used conveniently, saving you time and mistakes.

And yes, having the pop-up for the arguments or the docs of a function without actually completing it for you is nice. But you can also CTRL+click on a function name to jump to the definition (whether yours or part of a library or the core language) and you'll learn more about the context and flow of the function by doing that.