> For the complete documentation index, see [llms.txt](https://hubot.gitbook.io/hubot-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hubot.gitbook.io/hubot-whitepaper/introduction/background.md). # Background In the software development industry, writing code can be a laborious and time-consuming task. Developers often face challenges such as the need to constantly learn new technologies, search for relevant documentation, and write repetitive code. These hurdles can significantly slow down the development process and hinder productivity. To overcome these challenges and enhance development efficiency, we have created the Hubot project. While Hubot aims to revolutionize the development process with AI-generated code, there are inherent risks and challenges to consider. These include potential algorithmic biases, security vulnerabilities, and the need for continuous improvements to the AI models. Additionally, adoption and acceptance from the developer community may pose challenges that require strategic outreach and education efforts. Hubot is committed to addressing these risks and challenges to provide a seamless and reliable code generation experience. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://hubot.gitbook.io/hubot-whitepaper/introduction/background.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.