# 목차

[![](https://user-images.githubusercontent.com/101321313/218290576-a964125e-4e7f-482c-87e5-c0b6e6cc970b.png)](http://www.yes24.com/Product/Goods/11681152)

[여기에서도 볼 수 있어요](https://kukingclass.gitbook.io/cleancode/)

## 스터디 방식

정해진 진도까지 모두 읽어본 후 각자 맡은 부분을 정리해서 올리고 만나서 발표합니다.

그 후 서로 자유롭게 질문하고 얘기합니다.

## Table of contents

* 1장. 클린코드 [@mimwin](https://github.com/mimwin)
* 2장. 의미 있는 이름 [@Lee-Jiseung](https://github.com/Lee-Jiseung)
* 3장. 함수 [@goldggyul](https://github.com/goldggyul)
* 4장. 주석 [@janghoosa](https://github.com/janghoosa)
* 5장. 형식 맞추기 [@sujin-kk](https://github.com/sujin-kk)
* 6장. 객체와 자료 구조 [@LifesLike](https://github.com/LifesLike)
* 7장. 오류 처리
* 8장. 경계
* 9장. 단위 테스트
* 10장. 클래스
* 11장. 시스템 [@LifesLike](https://github.com/LifesLike)
* 12장. 창발성
* 13장. 동시성 [@LifesLike](https://github.com/LifesLike)
* 14장. 점진적인 개선


---

# Agent Instructions: 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:

```
GET https://kukingclass.gitbook.io/cleancode/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
