> For the complete documentation index, see [llms.txt](https://wiki.fruetel.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.fruetel.net/looking-back/2020-01.md). # 2020-01 * Got postgres up and running in my toy project kubernetes cluster. Managed to use it for the repository of my document storage service. * Slightly injured my chest/shoulder during a heavy bench press set at the beginning of January. Doesn't seem to be serious, but kept me from seriously benching most of the month. I think I've been working in the 2-3 rep range for too long. * Finally got my wisdom teeth extracted. They didn't cause any problems yet, but I'm sure they would have become an issue in the future. * Tried to establish a habit of journaling and performing regular day evaluation, but still struggle finding the time and energy to go through with it. * Made progress reading [Design Patterns in Ruby](https://www.amazon.de/Design-Patterns-Addison-Wesley-Professional-English-ebook/dp/B004YW6M6G) but did not manage to finish the book. I should spend more of my daily commute time reading books. --- # 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://wiki.fruetel.net/looking-back/2020-01.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.