{"success":true,"count":2,"items":[{"videoId":"fQmlML9Lay4","chunkIndex":0,"totalChunks":2,"title":"Conductor CEO Charlie Holtz Walks Us Through His AI Coding Setup — Part 1 of 2","thumbnail":"https://i.ytimg.com/vi/fQmlML9Lay4/maxresdefault.jpg","duration":995,"uploader":"Y Combinator","youtubeUrl":"https://www.youtube.com/watch?v=fQmlML9Lay4","keywords":["startup","ai-coding","developer-tools","product-design","automation","agentic-workflows","typescript","elixir","rust","workflow"],"normalizedKeywords":["엔지니어링","프로덕트","기술 트렌드"],"targetAudience":[{"who":"스타트업 창업자","why":"AI 시대에 제품 워크플로와 팀 운영을 어떻게 설계할지 배울 수 있음"},{"who":"개발자","why":"에이전트 기반 코딩, PR 중심 협업, 권한 설계 같은 실전 패턴이 많음"},{"who":"프로덕트 디자이너","why":"AI 도구의 인터페이스와 인간-에이전트 경계 설계 관점을 얻을 수 있음"}],"normalizedAudience":["창업자·스타트업","엔지니어·개발자","프로덕트 디자이너"],"summary":"이 영상에서 Charlie Holtz는 Conductor CEO로서 자신이 매일 사용하는 AI 코딩 환경과 작업 방식을 직접 보여준다. 핵심은 코드를 손으로 많이 쓰는 대신, 여러 AI 에이전트에 작업을 던지고, PR 단위로 검토·수정·머지하는 운영 방식이다. 그는 키보드 단축키, 음성 입력, 모바일에서의 원격 지시, 자동화된 워크스페이스 상태 관리 등을 통해 '개인이 아니라 작은 회사의 CEO처럼 에이전트들을 관리하는 경험'을 만들고 있다고 설명한다.\n\n동시에 그는 AI에게 모든 것을 맡기지 말아야 한다는 원칙도 강하게 강조한다. 아키텍처, 핵심 API, UI 결정처럼 인간이 의도적으로 설계해야 하는 영역과, AI에게 자유롭게 실험을 맡겨도 되는 영역을 분리해야 한다는 것이다. 또 모델이 점점 더 오래, 더 똑똑하게 실행되는 방향으로 가는 만큼, 지금의 제품과 워크플로도 그 미래에 맞춰 계속 바뀌어야 한다는 문제의식을 드러낸다.","insights":["AI 코딩의 핵심은 작성이 아니라 지시·검토·병합이다.","속도는 자동화보다 워크플로 설계에서 먼저 나온다.","AI에게 자유를 주되 핵심 경계는 인간이 잡아야 한다.","좋은 제품은 기능보다 '사람이 관리하기 쉬운 구조'에서 나온다.","미래의 개발 도구는 로컬 편의보다 긴 실행 환경을 전제로 해야 한다."],"keyClips":[{"clipId":"fQmlML9Lay4:c0:3-17","startSegmentIndex":3,"endSegmentIndex":17,"startTime":24.31,"endTime":116,"durationSeconds":91.7,"preview":"음성으로 일하는 법","mustSee":false},{"clipId":"fQmlML9Lay4:c0:18-23","startSegmentIndex":18,"endSegmentIndex":23,"startTime":116,"endTime":160.07999999999998,"durationSeconds":44.1,"preview":"실험이 곧 제품","mustSee":false},{"clipId":"fQmlML9Lay4:c0:24-34","startSegmentIndex":24,"endSegmentIndex":34,"startTime":160.07999999999998,"endTime":257.919,"durationSeconds":97.8,"preview":"에이전트 CEO 관점","mustSee":true},{"clipId":"fQmlML9Lay4:c0:43-57","startSegmentIndex":43,"endSegmentIndex":57,"startTime":298.4,"endTime":392.96,"durationSeconds":94.6,"preview":"인간 경계의 중요성","mustSee":true},{"clipId":"fQmlML9Lay4:c0:58-75","startSegmentIndex":58,"endSegmentIndex":75,"startTime":392.96,"endTime":528.48,"durationSeconds":135.5,"preview":"기술스택과 설계철학","mustSee":true},{"clipId":"fQmlML9Lay4:c0:76-84","startSegmentIndex":76,"endSegmentIndex":84,"startTime":528.48,"endTime":592.32,"durationSeconds":63.8,"preview":"미래를 향한 제약","mustSee":false}],"curatedSegments":[{"segmentIndex":38,"text":"Code is almost like uh sawdust now in that like it used to be that code was the thing you were building. You were putting time into like in into like crafting the code and now you're putting time into describing what you want and how you want it to be built.","startTime":899.04,"endTime":906,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"코드 가치 변화에 대한 강한 통찰."},{"segmentIndex":34,"text":"But the ideal is like you should feel like the CEO of a little company and you can see all your agents working for you and they'll bring you up like digestible reports and then you can point them in the right direction if they like need some correction or just merge it in if it looks good.","startTime":244.159,"endTime":257.919,"durationSeconds":14,"level":"B2","overallScore":8,"rationale":"제품 비전과 사용 철학이 잘 드러남."},{"segmentIndex":52,"text":"I think something that's really important to us is having like clear boundaries between uh well we call them slot free zones um and having like parts of the code base or like parts of the documentation that we like know is written by a human.","startTime":348.88,"endTime":360.88,"durationSeconds":12,"level":"B2","overallScore":7.8,"rationale":"AI 활용 경계 설정 원칙이 핵심적임."},{"segmentIndex":55,"text":"Um because if you're not careful like the AI can like get in a vicious cycle where like it sees bad code and then it writes more bad code as a result.","startTime":372.96,"endTime":382.479,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"AI 품질 악순환을 설명하는 통찰 문장."},{"segmentIndex":63,"text":"Another thing we talk about is like don't let the AI be your architect.","startTime":426.16,"endTime":429.44,"durationSeconds":3,"level":"B2","overallScore":7.6,"rationale":"AI 활용 원칙을 압축한 조언."},{"segmentIndex":68,"text":"And I think if you let the AI make your like UI choices for you, you can end up with something that like it just doesn't feel like crafted.","startTime":462.639,"endTime":469.12,"durationSeconds":6,"level":"B2","overallScore":7.8,"rationale":"AI에 맡긴 디자인의 위험을 짚음."},{"segmentIndex":73,"text":"I think something we would do a bit differently is building the core of the app um around like human written APIs and like contracts that the AI wouldn't contribute to as much.","startTime":501.12,"endTime":510.639,"durationSeconds":10,"level":"C1","overallScore":7.8,"rationale":"핵심 설계 원칙을 구체적으로 제시."},{"segmentIndex":74,"text":"And then I think that like it's important to have a big chunks of your codebase be like have like free reign for the AI where you can just like throw a ton of different ideas at it and know that it's like not going to affect the core infrastructure.","startTime":510.639,"endTime":522.8,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"AI 실험 구역 분리 원칙이 선명함."},{"segmentIndex":82,"text":"So we really like enforced our workflow. I think like what's exciting but also hard about where we're at is like we have to constantly adapt to where like the models are going.","startTime":562.959,"endTime":572.48,"durationSeconds":10,"level":"B2","overallScore":7.8,"rationale":"현재 AI 환경의 핵심 과제를 요약."},{"segmentIndex":84,"text":"But like feels like we're very quickly moving to a world where the agents are going to run for 10 times longer and they're going to be 10 times smarter and they're going to need to run in an environment that like isn't constrained by like your max like CPU.","startTime":580.32,"endTime":592.32,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"에이전트 미래상에 대한 전망 제시."},{"segmentIndex":12,"text":"Like I think humans are spatial visual creatures and like having a command line interface just like feels like it's feels very like restrictive and I think it maybe works for the AI brains better than the human brains. But I think just like I want to know that okay my chats are over here and my like review panel is here.","startTime":687.279,"endTime":699.279,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"인간 중심 UI 관점이 뚜렷한 통찰."},{"segmentIndex":33,"text":"like skills are very much like a first class thing in GStack and it's like it's there's some like interesting ideas there I think like especially around like onboarding and we've added actually a specific mode for him called Gary mode which by default does not collapse any of the tool calls so you can see all the tool calls are default on collapse and you can even actually see uh Gary's face here if you're in Gary's mode >> what feels obvious to you and your team that the rest of the world doesn't fully understand yet >> like I think there's like a lot of cool stuff to explore with like collaboration between humans and the AIs.","startTime":833.76,"endTime":867.68,"durationSeconds":34,"level":"C1","overallScore":8,"rationale":"제품 철학·온보딩 아이디어가 풍부함."},{"segmentIndex":40,"text":"And the code is almost just like sawdust that comes out of that process.","startTime":916.56,"endTime":920.079,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"핵심 비유를 재확인해 인상적이다."},{"segmentIndex":41,"text":"And like that leads to like a lot of like interesting conclusions. Like one of them is like really what matters is your prompts.","startTime":920.079,"endTime":926.079,"durationSeconds":6,"level":"B2","overallScore":7.8,"rationale":"비유에서 실천적 결론을 뽑아낸다."},{"segmentIndex":42,"text":"And like when the next generation of models come out, you can just like rerun your prompts again and then you'll get new code and the old code didn't really matter.","startTime":926.079,"endTime":933.12,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"모델 세대교체 관점의 통찰이 선명함."},{"segmentIndex":20,"text":"Most of them don't make it in. So like you can see we have like four PRs here that are in review, but like there's a bunch of random ideas that I've tried here that are in progress that you know may never see the light of day.","startTime":123.759,"endTime":136.239,"durationSeconds":12,"level":"B2","overallScore":7,"rationale":"실험 다수는 폐기된다는 현실 인사이트."},{"segmentIndex":46,"text":"You're probably used to writing enterprise code but that's not how we do things around here.","startTime":314.639,"endTime":319.039,"durationSeconds":4,"level":"B2","overallScore":7,"rationale":"스타트업식 개발 원칙이 잘 드러남."},{"segmentIndex":53,"text":"It's possible like that the a the AI can contribute to the slot free zones but like it has to be like every line has to be read by a human.","startTime":360.88,"endTime":369.52,"durationSeconds":9,"level":"B2","overallScore":7,"rationale":"예외 허용 조건을 구체적으로 설명함."},{"segmentIndex":57,"text":"We have like some lines in our codebase that are like do not touch if you are an AI like this is for human eyes only.","startTime":386.24,"endTime":392.96,"durationSeconds":7,"level":"B2","overallScore":7,"rationale":"인간 전용 구역 원칙이 인상적임."},{"segmentIndex":65,"text":"Like that's actually going to change soon. But even that like concept of a workspace like we as a human had to like think that through.","startTime":438.479,"endTime":445.599,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"인간 설계 판단의 중요성을 말함."}],"generatedAt":"2026-06-24T23:13:14.495Z","keyClipsTotalSec":505},{"videoId":"fQmlML9Lay4","chunkIndex":1,"totalChunks":2,"title":"Conductor CEO Charlie Holtz Walks Us Through His AI Coding Setup — Part 2 of 2","thumbnail":"https://i.ytimg.com/vi/fQmlML9Lay4/maxresdefault.jpg","duration":995,"uploader":"Y Combinator","youtubeUrl":"https://www.youtube.com/watch?v=fQmlML9Lay4","keywords":["ai-coding","developer-tools","software-design","product-ux","code-review","llm-workflows","startup","prompt-engineering","automation"],"normalizedKeywords":["엔지니어링","프로덕트","기술 트렌드"],"targetAudience":[{"who":"AI 개발자","why":"어떤 모델을 언제 쓰고, UI로 어떻게 작업을 묶을지 배울 수 있음"},{"who":"스타트업 창업자","why":"AI 도구를 제품화할 때 어떤 경험과 철학이 중요한지 볼 수 있음"},{"who":"프로덕트 매니저","why":"개발자 워크플로우를 바꾸는 제품 결정과 사용자 경험 관점을 얻을 수 있음"}],"normalizedAudience":["엔지니어·개발자","창업자·스타트업","프로덕트 매니저·기획자"],"summary":"이 영상은 Conductor CEO가 자신의 AI 코딩 작업 흐름을 설명하며, 어떤 모델을 언제 쓰는지와 왜 터미널보다 시각적 UI가 더 낫다고 보는지를 중심으로 이야기한다. 그는 Codex는 묵직한 문제 해결용 워크호스, Claude Opus는 더 창의적이고 파트너 같은 존재로 구분하며, 상황에 따라 모델을 바꿔 쓴다고 말한다. 또한 토큰 사용은 아끼지 않지만 코드 라인은 최소화해야 코드베이스가 망가지지 않는다고 강조한다.\n\n후반부에서는 Conductor의 UX가 단순한 편의 기능이 아니라 인간의 인지 방식에 맞춘 설계라고 설명하고, 코드 자체보다 프롬프트와 워크플로우가 더 중요해지는 미래를 그린다. 코드는 결과물의 부산물(sawdust)이며, 소프트웨어는 게임 모드처럼 각자가 약간씩 커스터마이즈할 수 있는 'malleable software'로 진화할 것이라는 관점을 제시한다.","insights":["AI 도구는 모델 성격에 따라 역할을 분리해야 효율이 높다.","좋은 개발 도구는 기능보다 '손에 익는 느낌'으로 판단된다.","토큰은 써도 코드 라인은 줄여야 코드베이스가 무너지지 않는다.","터미널보다 UI가 중요한 이유는 인간이 시각적 존재이기 때문이다.","미래의 핵심 자산은 코드보다 프롬프트와 워크플로우가 된다."],"keyClips":[{"clipId":"fQmlML9Lay4:c1:1-3","startSegmentIndex":1,"endSegmentIndex":3,"startTime":600.23,"endTime":640.079,"durationSeconds":39.8,"preview":"직감으로 고르는 UX","mustSee":false},{"clipId":"fQmlML9Lay4:c1:4-10","startSegmentIndex":4,"endSegmentIndex":10,"startTime":640.079,"endTime":678,"durationSeconds":37.9,"preview":"모델별 역할 분리","mustSee":false},{"clipId":"fQmlML9Lay4:c1:11-15","startSegmentIndex":11,"endSegmentIndex":15,"startTime":678,"endTime":721.36,"durationSeconds":43.4,"preview":"터미널보다 UI","mustSee":false},{"clipId":"fQmlML9Lay4:c1:16-23","startSegmentIndex":16,"endSegmentIndex":23,"startTime":721.36,"endTime":773.8389999999999,"durationSeconds":52.5,"preview":"토큰은 쓰고 코드는 줄여라","mustSee":true},{"clipId":"fQmlML9Lay4:c1:24-28","startSegmentIndex":24,"endSegmentIndex":28,"startTime":773.8389999999999,"endTime":805.04,"durationSeconds":31.2,"preview":"리뷰 흐름의 재설계","mustSee":false},{"clipId":"fQmlML9Lay4:c1:29-33","startSegmentIndex":29,"endSegmentIndex":33,"startTime":805.04,"endTime":867.68,"durationSeconds":62.6,"preview":"사용자가 확장한다","mustSee":false},{"clipId":"fQmlML9Lay4:c1:34-49","startSegmentIndex":34,"endSegmentIndex":49,"startTime":867.68,"endTime":992.079,"durationSeconds":124.4,"preview":"프롬프트가 제품이다","mustSee":true}],"curatedSegments":[{"segmentIndex":38,"text":"Code is almost like uh sawdust now in that like it used to be that code was the thing you were building. You were putting time into like in into like crafting the code and now you're putting time into describing what you want and how you want it to be built.","startTime":899.04,"endTime":906,"durationSeconds":7,"level":"C1","overallScore":8.8,"rationale":"코드 가치 변화에 대한 강한 통찰."},{"segmentIndex":34,"text":"But the ideal is like you should feel like the CEO of a little company and you can see all your agents working for you and they'll bring you up like digestible reports and then you can point them in the right direction if they like need some correction or just merge it in if it looks good.","startTime":244.159,"endTime":257.919,"durationSeconds":14,"level":"B2","overallScore":8,"rationale":"제품 비전과 사용 철학이 잘 드러남."},{"segmentIndex":52,"text":"I think something that's really important to us is having like clear boundaries between uh well we call them slot free zones um and having like parts of the code base or like parts of the documentation that we like know is written by a human.","startTime":348.88,"endTime":360.88,"durationSeconds":12,"level":"B2","overallScore":7.8,"rationale":"AI 활용 경계 설정 원칙이 핵심적임."},{"segmentIndex":55,"text":"Um because if you're not careful like the AI can like get in a vicious cycle where like it sees bad code and then it writes more bad code as a result.","startTime":372.96,"endTime":382.479,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"AI 품질 악순환을 설명하는 통찰 문장."},{"segmentIndex":63,"text":"Another thing we talk about is like don't let the AI be your architect.","startTime":426.16,"endTime":429.44,"durationSeconds":3,"level":"B2","overallScore":7.6,"rationale":"AI 활용 원칙을 압축한 조언."},{"segmentIndex":68,"text":"And I think if you let the AI make your like UI choices for you, you can end up with something that like it just doesn't feel like crafted.","startTime":462.639,"endTime":469.12,"durationSeconds":6,"level":"B2","overallScore":7.8,"rationale":"AI에 맡긴 디자인의 위험을 짚음."},{"segmentIndex":73,"text":"I think something we would do a bit differently is building the core of the app um around like human written APIs and like contracts that the AI wouldn't contribute to as much.","startTime":501.12,"endTime":510.639,"durationSeconds":10,"level":"C1","overallScore":7.8,"rationale":"핵심 설계 원칙을 구체적으로 제시."},{"segmentIndex":74,"text":"And then I think that like it's important to have a big chunks of your codebase be like have like free reign for the AI where you can just like throw a ton of different ideas at it and know that it's like not going to affect the core infrastructure.","startTime":510.639,"endTime":522.8,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"AI 실험 구역 분리 원칙이 선명함."},{"segmentIndex":82,"text":"So we really like enforced our workflow. I think like what's exciting but also hard about where we're at is like we have to constantly adapt to where like the models are going.","startTime":562.959,"endTime":572.48,"durationSeconds":10,"level":"B2","overallScore":7.8,"rationale":"현재 AI 환경의 핵심 과제를 요약."},{"segmentIndex":84,"text":"But like feels like we're very quickly moving to a world where the agents are going to run for 10 times longer and they're going to be 10 times smarter and they're going to need to run in an environment that like isn't constrained by like your max like CPU.","startTime":580.32,"endTime":592.32,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"에이전트 미래상에 대한 전망 제시."},{"segmentIndex":12,"text":"Like I think humans are spatial visual creatures and like having a command line interface just like feels like it's feels very like restrictive and I think it maybe works for the AI brains better than the human brains. But I think just like I want to know that okay my chats are over here and my like review panel is here.","startTime":687.279,"endTime":699.279,"durationSeconds":12,"level":"C1","overallScore":8,"rationale":"인간 중심 UI 관점이 뚜렷한 통찰."},{"segmentIndex":33,"text":"like skills are very much like a first class thing in GStack and it's like it's there's some like interesting ideas there I think like especially around like onboarding and we've added actually a specific mode for him called Gary mode which by default does not collapse any of the tool calls so you can see all the tool calls are default on collapse and you can even actually see uh Gary's face here if you're in Gary's mode >> what feels obvious to you and your team that the rest of the world doesn't fully understand yet >> like I think there's like a lot of cool stuff to explore with like collaboration between humans and the AIs.","startTime":833.76,"endTime":867.68,"durationSeconds":34,"level":"C1","overallScore":8,"rationale":"제품 철학·온보딩 아이디어가 풍부함."},{"segmentIndex":40,"text":"And the code is almost just like sawdust that comes out of that process.","startTime":916.56,"endTime":920.079,"durationSeconds":4,"level":"B2","overallScore":7.6,"rationale":"핵심 비유를 재확인해 인상적이다."},{"segmentIndex":41,"text":"And like that leads to like a lot of like interesting conclusions. Like one of them is like really what matters is your prompts.","startTime":920.079,"endTime":926.079,"durationSeconds":6,"level":"B2","overallScore":7.8,"rationale":"비유에서 실천적 결론을 뽑아낸다."},{"segmentIndex":42,"text":"And like when the next generation of models come out, you can just like rerun your prompts again and then you'll get new code and the old code didn't really matter.","startTime":926.079,"endTime":933.12,"durationSeconds":7,"level":"B2","overallScore":7.8,"rationale":"모델 세대교체 관점의 통찰이 선명함."},{"segmentIndex":20,"text":"Most of them don't make it in. So like you can see we have like four PRs here that are in review, but like there's a bunch of random ideas that I've tried here that are in progress that you know may never see the light of day.","startTime":123.759,"endTime":136.239,"durationSeconds":12,"level":"B2","overallScore":7,"rationale":"실험 다수는 폐기된다는 현실 인사이트."},{"segmentIndex":46,"text":"You're probably used to writing enterprise code but that's not how we do things around here.","startTime":314.639,"endTime":319.039,"durationSeconds":4,"level":"B2","overallScore":7,"rationale":"스타트업식 개발 원칙이 잘 드러남."},{"segmentIndex":53,"text":"It's possible like that the a the AI can contribute to the slot free zones but like it has to be like every line has to be read by a human.","startTime":360.88,"endTime":369.52,"durationSeconds":9,"level":"B2","overallScore":7,"rationale":"예외 허용 조건을 구체적으로 설명함."},{"segmentIndex":57,"text":"We have like some lines in our codebase that are like do not touch if you are an AI like this is for human eyes only.","startTime":386.24,"endTime":392.96,"durationSeconds":7,"level":"B2","overallScore":7,"rationale":"인간 전용 구역 원칙이 인상적임."},{"segmentIndex":65,"text":"Like that's actually going to change soon. But even that like concept of a workspace like we as a human had to like think that through.","startTime":438.479,"endTime":445.599,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"인간 설계 판단의 중요성을 말함."}],"generatedAt":"2026-06-24T23:13:36.296Z","keyClipsTotalSec":505}]}