# Step 2: Choosing your Code Editor

Ok ok, yes, maybe this wasn’t needed but I feel it is. Choosing a code editor is very important. You need to be able to feel comfortable, your eyes need to have nice blends of colors to look at, and most importantly, you need some IntelliSense to help you :).

Ok so how do you choose? Here ya go.

## [**Visual Studio Code (not Visual Studio)**](https://code.visualstudio.com/)

This is personally one of my favorites. There are so so so so so many extensions and themes to choose from, ranging from git to formatting documents, and coloring text and brackets. It's amazing. You can even have Discord Rich Presence in there! It also has IntelliSense. 

VSC is developed by Microsoft, and is far more lightweight than Visual Studio which is intended for .NET applications.

## [**WebStorm**](https://www.jetbrains.com/webstorm/)

This is another favorite of mine, but not cheap if you don’t have the [Github Student Developer Pack](https://education.github.com/pack). That one gets you it for free like me. It has an amazing IntelliSense, which is a menu that pops under your code suggesting certain things and detecting mistakes such as incorrect spelling, undefined variables, reassigning a constant, and tons more.

WebStorm is developed by JetBrains.

## [**Sublime Text 2/3**](https://www.sublimetext.com/)

This is a good quick and fast text editor in my opinion. It can be used for lots of things, but I feel as if VSCode and Webstorm absolutely destroy Sublime Text 2 and 3. Again, it is an amazing on the fly code editor. But when you are at a desktop, all day, you may want something more customized to your desires.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://vinniehat-1.gitbook.io/guide-to-making-your-own-discord-bot/guide/code-editor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.