# 7. Not picking the right tools Everyone has their favorite set of tools. Each tool is great for a specific task, while others may not be as effective. For example, a hammer is perfect for hammering a nail, but not so great for screwing in a self-tapping screw. It's important not to use a tool simply because it's popular or because you love it. This is a common mistake made by beginners. If you only know a few tools, even the "best" one on your list may not be the best for the job at hand. That's why it's important to always broaden your horizons and be open to learning new tools. Some coders may feel comfortable with the tools they know and may not want to learn new ones. However, this is a mistake. You can build a house with primitive tools from your old pantry, but it will take a lot of time and effort. On the other hand, investing in new tools can help you build a house much faster, better, and more beautifully. Since tools are constantly evolving and new ones are emerging, it's important to get used to constantly learning and using them. Don't be afraid to try new tools and experiment with different approaches. This will help you become a better coder and achieve your goals more efficiently. --- # 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://tester-ai.gitbook.io/en/12.-developers-mistakes/7.-not-picking-the-right-tools.md?ask= ``` 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.