더 나은 프로그래머 되는법 2주차 - 하업서 #540
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @hemil0102, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
This pull request contains answers to questions from the book 'Becoming a Better Programmer' for chapters 9 to 13. The author, hemil0102, reflects on topics such as handling unexpected situations, debugging, testing, managing complexity, and system architecture. The answers are based on the author's experiences and understanding of the concepts.
Highlights
- Error Handling: The author discusses the importance of robust error handling and when it might be acceptable to forgo strict error handling.
- Debugging: The author evaluates their time spent on debugging and differentiates between debugging new and existing code.
- Testing: The author shares their experiences with different types of testing and their thoughts on test-driven development (TDD).
- Complexity: The author reflects on code simplicity, the nature of connections in code, and how to address complexity arising from interpersonal issues.
- System Architecture: The author shares their views on the best and worst system architectures they have encountered and assesses their current project's architecture.
Changelog
- 2025/Becoming a Better Programmer/hemil0102/9~13장.md
- Added answers to questions related to pair programming.
- Answered questions from Chapter 9 about handling unexpected situations in code.
- Answered questions from Chapter 10 about debugging practices and strategies.
- Answered questions from Chapter 11 about testing methodologies and the role of QA.
- Answered questions from Chapter 12 about managing complexity in software design.
- Answered questions from Chapter 13 about system architecture and design principles.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
A programmer's quest,
To write code that's the best,
With tests in the mix,
And complexity nix,
A clean system, put to the test.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
|
우측에 있는 |
There was a problem hiding this comment.
Code Review
The pull request consists of answers to questions from the book 'Becoming a Better Programmer'. The responses demonstrate thoughtful engagement with the material. However, some answers could be more specific and actionable.
Merge Readiness
The pull request is a reflection on the book 'Becoming a Better Programmer' and doesn't contain any code changes that would directly impact a codebase. Therefore, it's more about personal learning and understanding. I am unable to approve the pull request in any circumstance, and that users should have others review and approve this code before merging. There are no critical or high severity issues, so merging is appropriate.
hemil0102
requested review from
jongfeel,
TaeHyoungKwon,
ymkim97,
aquamagic9,
fkdl0048,
tttghost and
dhlee3994
| @@ -0,0 +1,79 @@ | |||
| # 논제 | |||
| 페어프로그래밍을 해본적이 있는가? 해봤다면 장단점을 이야기 해봅니다. | |||
There was a problem hiding this comment.
42서울에서 프로젝트를 진행할 때 짧게 해본 경험이 있습니다.
장점으로는 막히는 부분이 생기면 대화를 통해 좀 더 빠르게 문제점에 다가갈 수 있었으며 실수가 확실히 줄어들었습니다.
단점으로는 피로도가 생각보다 높았고 오래지속하기 어렵다고 느꼈습니다. 그래서 의논이 필요한 정말 중요한 부분에 대해서 페어프로그래밍을 진행한다면 좀 더 효율적이라고 생각했고 코더와 지시자의 역할 교환을 통해 피로도를 낮출 수 있었습니다.
There was a problem hiding this comment.
회사에서 해본 적은 없고, 스터디하면서 해봤습니다. 생각의 불일치를 확인하고 바로잡을 수 있었던 것이 가장 큰 장점이었습니다.
| @@ -0,0 +1,79 @@ | |||
| # 논제 | |||
| 페어프로그래밍을 해본적이 있는가? 해봤다면 장단점을 이야기 해봅니다. | |||
There was a problem hiding this comment.
회사에서 해본 적은 없고, 스터디하면서 해봤습니다. 생각의 불일치를 확인하고 바로잡을 수 있었던 것이 가장 큰 장점이었습니다.
| @@ -0,0 +1,79 @@ | |||
| # 논제 | |||
| 페어프로그래밍을 해본적이 있는가? 해봤다면 장단점을 이야기 해봅니다. | |||
There was a problem hiding this comment.
간단하게 코멘트로 하기 보다는 코드 수정을 하면서 얘기해야 할 필요가 있을 때 하는 것 같습니다.
유일한 단점은 시간 관리를 못한다는 것인데, 시간이 오래 걸리는 문제를 해결할 수 있다면 장점이 훨씬 많은 방법입니다.
몸 컨디션이 좋지 않아서 늦게 올려 죄송합니다.
저번과 마찬가지로 질문에 대한 답변을 적어보았습니다.