> 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/5-bibliography.md).

# Appendix A - Bibliography/Websiteography

## Books

\[Rules00] Guy Kawasaki, Michelle Moreno, and Gary Kawasaki. 2000. HarperBusiness. Rules for Revolutionaries: The Capitalist Manifesto for Creating and Marketing New Products and Services.

\[RDev96] Steve McConnell. 1996. Microsoft Press. Redmond, Wash. Rapid Development: Taming Wild Software Schedules.

\[CodeC93] Steve McConnell. 1993. Microsoft Press. Redmond, Wash. Code Complete.

\[XP99] Kent Beck. 1999. 0201616416. Addison-Wesley. Extreme Programming Explained: Embrace Change.

\[PlanXP00] Kent Beck and Martin Fowler. 2000. 0201710919. Addison-Wesley. Planning Extreme Programming.

\[Prag99] Andrew Hunt, David Thomas, and Ward Cunningham. 1999. 020161622X. Addison-Wesley. The Pragmatic Programmer: From Journeyman to Master.

\[Stronger] Friedrich Nietzsche. 1889. Twilight of the Idols, "Maxims and Arrows", section 8..

## Web Sites

\[PGSite] Paul Graham. 2002. Articles on his website: <http://www.paulgraham.com/articles.html>. All of them, but especially "Beating the Averages".

\[Hacker] Eric S. Raymond. 2003. How to Become a Hacker. <http://www.catb.org/~esr/faqs/hacker-howto.html>.

\[HackDict] Eric S. Raymond. 2003. The New Hacker Dictionary. <http://catb.org/esr/jargon/jargon.html>.

\[ExpCS] Edsger W. Dijkstra. 1986. How Experimental is Computing Science?. <http://www.cs.utexas.edu/users/EWD/ewd09xx/EWD988a.PDF>.

\[Knife] Edsger W. Dijkstra. 1984. On a Cultural Gap. <http://www.cs.utexas.edu/users/EWD/ewd09xx/EWD913.PDF>.

Next [History](/how-to-be-a-programmer/jp/6-history.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/5-bibliography.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.