Claude Code 세션을 하나만 실행한다면 속도가 충분히 빠르지 않습니다.
hackernews
|
|
🔬 연구
#claude
#review
원문 출처: hackernews · Genesis Park에서 요약 및 분석
요약
에이전트 코딩의 핵심 기술은 코드 작성이 아니라 관리 능력에 있으므로, 엔지니어를 관리하는 매니저처럼 생각해야 합니다. AI는 직접 테스트할 수 없으므로 사용자가 QA를 담당하고 문제를 해결해주며, 코드 검토는 PR 생성 후에 수행해야 합니다. 반복 가능한 프로세스와 적절한 프롬프트를 활용하면 여러 세션을 효율적으로 운영할 수 있으며, 비용 절감을 넘어 더 나은 품질의 제품을 구축할 수 있게 됩니다.
본문
The real skill in using agentic coding is not coding at all. It's management. Think like a manager, not an engineer Imagine you're managing some number of engineers. They're coding. They ask you questions and you tell them what to do, what to write, or what architectural path to take. But you are not writing the code. And you are not even watching them write the code. This is important because that's what real life is as a manager. You're not watching everybody write the code. The difference, because these agents are not people, is that they can't test like a person. Your job: unblock and QA As their manager, you must unblock them. You have to be their QA. You have to work with them until their feature works. Only after the PR is created, that is when you review the code. And just like with people, you ask for changes, or you approve it. There's nothing unique about AI-generated code. You must be the gating qualitative factor. And if the AI produced garbage, no big deal. Have it try again and improve the prompt. There is no point in reviewing the code before the PR. You would never review the code before a PR for someone you manage, unless they asked. (Or you don't trust them, but that's a model and prompting discussion, not the point of this post.) It becomes manageable with a process The skill of using AI is how many sessions you can effectively pilot at once. And this becomes manageable with a repeatable process. Just like scrum, waterfall, and agile before it, AI development processes are emerging. Prompting and planning plugins like Superpowers, GSD, spec-kit, and Compound Engineering can create the foundation for repeatable, reliable output. But those are just frameworks. The key is the prompts and instructions you and your team write. I'm not sure how to justify working on one thing at a time anymore. And when the cost of building drops, you don't just ship more. You build better. The details you always wanted to get right, you finally can. Resources - Superpowers - AI-native development workflow - GSD (Get Shit Done) - structured prompting for Claude Code - spec-kit - specification-driven development - Compound Engineering - multi-agent development plugin Scape and its creator are not affiliated with or connected to any of these projects.
Genesis Park 편집팀이 AI를 활용하여 작성한 분석입니다. 원문은 출처 링크를 통해 확인할 수 있습니다.
공유