> For the complete documentation index, see [llms.txt](https://incheol-jung.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://incheol-jung.gitbook.io/docs/q-and-a/seminar.md).

# SEMINAR

- [2022 INFCON 후기](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon.md): 2022 INFCON 후기
- [\[104호\] 사이드 프로젝트 만세! - 기술만큼 중요했던 제품과 팀 성장기](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/104.md)
- [\[102호\] 팀을 넘어서 전사적 협업 환경 구축하기](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/102.md)
- [\[103호\] 코드 리뷰의 또 다른 접근 방법: Pull Requests vs. Stacked Changes](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/103-pull-requests-vs.-stacked-changes.md)
- [\[105호\] 실전! 멀티 모듈 프로젝트 구조와 설계](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/105.md)
- [\[105호\] 지금 당장 DevOps를 해야 하는 이유](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/105-devops.md)
- [\[102호\] (레거시 시스템) 개편의 기술 - 배달 플랫폼에서 겪은 N번의 개편 경험기](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/102-n.md)
- [\[102호\] 서버비 0원, 클라우드 큐 도입으로 해냈습니다!](https://incheol-jung.gitbook.io/docs/q-and-a/seminar/2022-infcon/102-0.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://incheol-jung.gitbook.io/docs/q-and-a/seminar.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.