> For the complete documentation index, see [llms.txt](https://braydie.gitbook.io/how-to-be-a-programmer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://braydie.gitbook.io/how-to-be-a-programmer/en/3-advanced.md).

# 3. Advanced

* Technological Judgment
  * [How to Tell the Hard From the Impossible](/how-to-be-a-programmer/en/3-advanced/technical-judgment/01-how-to-tell-the-hard-from-the-impossible.md)
  * [How to Utilize Embedded Languages](/how-to-be-a-programmer/en/3-advanced/technical-judgment/02-how-to-utilize-embedded-languages.md)
  * [Choosing Languages](/how-to-be-a-programmer/en/3-advanced/technical-judgment/03-choosing-languages.md)
* Compromising Wisely
  * [How to Fight Schedule Pressure](/how-to-be-a-programmer/en/3-advanced/compromising-wisely/01-how-to-fight-schedule-pressure.md)
  * [How to Understand the User](/how-to-be-a-programmer/en/3-advanced/compromising-wisely/02-how-to-understand-the-user.md)
  * [How to Get a Promotion](/how-to-be-a-programmer/en/3-advanced/compromising-wisely/03-how-to-get-a-promotion.md)
* Serving Your Team
  * [How to Develop Talent](/how-to-be-a-programmer/en/3-advanced/serving-your-team/01-how-to-develop-talent.md)
  * [How to Choose What to Work On](/how-to-be-a-programmer/en/3-advanced/serving-your-team/02-how-to-choose-what-to-work-on.md)
  * [How to Get the Most From Your Team-mates](/how-to-be-a-programmer/en/3-advanced/serving-your-team/03-how-to-get-the-most-from-your-teammates.md)
  * [How to Divide Problems Up](/how-to-be-a-programmer/en/3-advanced/serving-your-team/04-how-to-divide-problems-up.md)
  * [How to Handle Boring Tasks](/how-to-be-a-programmer/en/3-advanced/serving-your-team/05-how-to-handle-boring-tasks.md)
  * [How to Gather Support for a Project](/how-to-be-a-programmer/en/3-advanced/serving-your-team/06-how-to-gather-support-for-a-project.md)
  * [How to Grow a System](/how-to-be-a-programmer/en/3-advanced/serving-your-team/07-how-to-grow-a-system.md)
  * [How to Communicate Well](/how-to-be-a-programmer/en/3-advanced/serving-your-team/08-how-to-communicate-well.md)
  * [How to Tell People Things They Don't Want to Hear](/how-to-be-a-programmer/en/3-advanced/serving-your-team/09-how-to-tell-people-things-they-dont-want-to-hear.md)
  * [How to Deal with Managerial Myths](/how-to-be-a-programmer/en/3-advanced/serving-your-team/10-how-to-deal-with-managerial-myths.md)
  * [How to Deal with Organizational Chaos](/how-to-be-a-programmer/en/3-advanced/serving-your-team/11-how-to-deal-with-organizational-chaos.md)


---

# 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://braydie.gitbook.io/how-to-be-a-programmer/en/3-advanced.md?ask=<question>&goal=<endgoal>
```

`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.