{"success":true,"count":3,"items":[{"videoId":"SlGRN8jh2RI","chunkIndex":0,"totalChunks":3,"title":"Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next — Part 1 of 3","thumbnail":"https://i.ytimg.com/vi/SlGRN8jh2RI/maxresdefault.jpg","duration":1476,"uploader":"Sequoia Capital","youtubeUrl":"https://www.youtube.com/watch?v=SlGRN8jh2RI","keywords":["ai-coding","software-development","developer-tools","agentic-workflows","product-strategy","typescript","react","automation","future-of-work"],"normalizedKeywords":["엔지니어링","프로덕트","기술 트렌드"],"targetAudience":[{"who":"엔지니어","why":"AI 에이전트가 코딩을 어디까지 대체하는지와 실전 운영법을 배울 수 있음"},{"who":"창업자","why":"신제품이 어떤 기술/제품 흐름 위에서 만들어지는지 감을 잡을 수 있음"},{"who":"프로덕트 매니저","why":"개발 생산성 변화가 팀 구조와 협업 방식에 미치는 영향을 이해할 수 있음"}],"normalizedAudience":["엔지니어·개발자","창업자·스타트업","프로덕트 매니저·기획자"],"summary":"이 영상은 Claude Code의 탄생 배경과, AI가 소프트웨어 개발을 얼마나 바꿔 놓았는지에 대한 Boris Cherny의 관점을 중심으로 진행된다. 그는 초기에는 단순한 type-ahead 수준이던 코딩 보조가 곧 에이전트가 코드를 전부 작성하는 단계로 넘어갈 것이라 보고, 실제로 Claude Code를 '미래 모델에 맞춰 미리 만든 제품'으로 설계했다고 설명한다. 다만 첫 6개월은 거의 쓸 수 없었고, Opus 4 이후 모델 성능이 올라가며 폭발적으로 성장했다는 점을 강조한다.\n\n또한 그는 자신의 작업 방식이 지금은 거의 전부 에이전트와 루프(loop), routines 같은 자동화 시스템으로 운영된다고 말한다. 개인적으로는 여러 세션과 수백~수천 개의 에이전트를 돌리며 PR 관리, CI 복구, 트위터 피드백 수집까지 맡기고 있고, 이런 루프형 작업 방식이 앞으로의 표준이 될 것이라고 본다. 마지막으로 팀의 미래는 더 많은 일반화와 교차분야 역량을 요구하게 될 것이며, 엔지니어가 디자인·데이터·제품을 함께 다루는 형태로 진화할 것이라는 전망을 제시한다.","insights":["AI 코딩은 도구가 아니라 팀의 운영 방식 자체를 바꾼다.","초기엔 PMF가 없어도 다음 모델을 보고 미리 만들 수 있다.","코딩이 '해결'됐다는 뜻은 일부는 이미 에이전트가 100% 쓴다는 말이다.","루프와 routines는 반복 업무를 상시 자동화하는 핵심 패턴이다.","미래의 강한 인재는 엔지니어를 넘어 제품·디자인을 넘나든다."],"keyClips":[{"clipId":"SlGRN8jh2RI:c0:28-55","startSegmentIndex":28,"endSegmentIndex":55,"startTime":157.8,"endTime":304.36,"durationSeconds":146.6,"preview":"Claude Code의 탄생","mustSee":true},{"clipId":"SlGRN8jh2RI:c0:61-73","startSegmentIndex":61,"endSegmentIndex":73,"startTime":347.6,"endTime":407.15999999999997,"durationSeconds":59.6,"preview":"코딩은 이미 바뀌었다","mustSee":false},{"clipId":"SlGRN8jh2RI:c0:76-98","startSegmentIndex":76,"endSegmentIndex":98,"startTime":416.4,"endTime":530.28,"durationSeconds":113.9,"preview":"에이전트식 작업법","mustSee":true},{"clipId":"SlGRN8jh2RI:c0:101-110","startSegmentIndex":101,"endSegmentIndex":110,"startTime":544.68,"endTime":608.44,"durationSeconds":63.8,"preview":"팀의 미래 인재상","mustSee":false}],"curatedSegments":[{"segmentIndex":43,"text":"So, we don't have to do type ahead anymore, we can just have the agent write all of the code.","startTime":234.92000000000002,"endTime":240.8,"durationSeconds":6,"level":"B2","overallScore":8,"rationale":"패러다임 전환을 압축해 말한 핵심 주장."},{"segmentIndex":50,"text":"But essentially, we were trying to build this thing that was like pre-PMF, and we knew that it wouldn't have PMF for 6 months because we were building for the next model.","startTime":276.88,"endTime":283.96,"durationSeconds":7,"level":"C1","overallScore":8,"rationale":"미래 모델을 선행해 제품화한 통찰이 큼."},{"segmentIndex":16,"text":"So, I think like by a couple years from now, the model is just going to be doing all the code. It's going to be starting the agents. It's going to be building the environments.","startTime":1296.16,"endTime":1302.16,"durationSeconds":6,"level":"B2","overallScore":7.6,"rationale":"미래상 예측이 강하고 명확함."},{"segmentIndex":38,"text":"Uh there's this idea that the model can do all the stuff that no product has yet captured.","startTime":210.96,"endTime":215.64,"durationSeconds":5,"level":"C1","overallScore":7,"rationale":"모델 능력과 제품화 간 격차를 통찰적으로 설명."},{"segmentIndex":42,"text":"But the feeling was we could actually go a lot further than that. And the model was almost ready for the next big step.","startTime":229.16,"endTime":234.92000000000002,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"기술 가능성 판단이 드러나는 핵심 문장."},{"segmentIndex":58,"text":"Uh if this is one of the three best from Anthropic, can you tell us more about what you mean by that, and what might still not be solved, or what second-order problems might come?","startTime":312.28,"endTime":320.44,"durationSeconds":8,"level":"C1","overallScore":7.2,"rationale":"핵심 주장과 후속 문제를 깊게 여는 질문."},{"segmentIndex":71,"text":"I was just trying to kind of push to see how far I can get it. Um but yeah, it's like for me it's just solved. Um but this is not the case everywhere. There's very big complicated code bases.","startTime":392.4,"endTime":398.15999999999997,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"개인 판단과 한계 인식이 함께 담김."},{"segmentIndex":91,"text":"And at [snorts] this point, I have like dozens of loops that are running for stuff. So, I have one that's babysitting my PRs, like fixing CI, auto-rebasing.","startTime":495.64,"endTime":498.84,"durationSeconds":3,"level":"C1","overallScore":7.2,"rationale":"구체 사례와 생생한 표현이 풍부하다."},{"segmentIndex":96,"text":"I sort of feel like loops are the future at this point. If you haven't experimented with it, highly recommend it.","startTime":517.08,"endTime":522.24,"durationSeconds":5,"level":"B2","overallScore":7,"rationale":"의견과 권유가 분명해 학습가치 높다."},{"segmentIndex":102,"text":"I feel like the way that things are going is generally there's going to be a lot more generalists than there are today.","startTime":552.84,"endTime":560.4,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"미래 인력 구조에 대한 핵심 전망이다."},{"segmentIndex":106,"text":"But I think the thing that we're going to start to see a lot more of is generalists that are cross-disciplinary.","startTime":575.28,"endTime":580.72,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"미래 변화 방향을 압축해 제시한다."},{"segmentIndex":61,"text":"It's knowing the domain that's the hard part.","startTime":1035.56,"endTime":1044.669,"durationSeconds":9,"level":"B2","overallScore":6.4,"rationale":"핵심 원리를 짚는 짧은 통찰."},{"segmentIndex":69,"text":"I think on the product side, there's probably a far larger gap. And that's just related to us changing all of our processes.","startTime":1090.36,"endTime":1096.56,"durationSeconds":6,"level":"B2","overallScore":6.8,"rationale":"제품 격차의 원인을 짚는 문장."},{"segmentIndex":71,"text":"And our Claudes are talking all day like as I'm coding, as my Claudes are coding in a loop, they will communicate over Slack to talk to other people's Claudes that are also running in a loop to kind of figure out unknowns.","startTime":1100.12,"endTime":1110.88,"durationSeconds":11,"level":"C1","overallScore":7.2,"rationale":"작업 방식 묘사와 표현 모두 풍부."},{"segmentIndex":72,"text":"We have no more manually written code anywhere at the company.","startTime":1110.88,"endTime":1113.96,"durationSeconds":3,"level":"B2","overallScore":6.4,"rationale":"강한 주장으로 조직 변화를 보여줌."},{"segmentIndex":5,"text":"And then it uses the Slack MCP to do that. So, so I think actually over time, it's not on users to figure out how to hold the tools better.","startTime":1221.52,"endTime":1228.48,"durationSeconds":7,"level":"B2","overallScore":7,"rationale":"책임 주체에 대한 관점 제시."},{"segmentIndex":6,"text":"And if that's the case, it's actually a product design problem and like I'm not doing a good job.","startTime":1228.48,"endTime":1232.52,"durationSeconds":4,"level":"B2","overallScore":7,"rationale":"문제 원인 재정의가 분명함."},{"segmentIndex":7,"text":"It's really on the model to do this stuff better and on us kind of prompting it so it naturally does this.","startTime":1232.52,"endTime":1243.31,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"역할 분담에 대한 핵심 주장."},{"segmentIndex":14,"text":"I think maybe like kind of the most fundamental way to answer that is it doesn't matter.","startTime":1288.6,"endTime":1293,"durationSeconds":4,"level":"B1","overallScore":6.6,"rationale":"핵심 입장을 압축해 보여줌."},{"segmentIndex":18,"text":"These I don't think these will be decisions that we are making as engineers anymore.","startTime":1306.64,"endTime":1311.16,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"엔지니어 역할 변화 통찰 제시."}],"generatedAt":"2026-06-25T00:03:03.550Z","keyClipsTotalSec":746},{"videoId":"SlGRN8jh2RI","chunkIndex":1,"totalChunks":3,"title":"Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next — Part 2 of 3","thumbnail":"https://i.ytimg.com/vi/SlGRN8jh2RI/maxresdefault.jpg","duration":1476,"uploader":"Sequoia Capital","youtubeUrl":"https://www.youtube.com/watch?v=SlGRN8jh2RI","keywords":["ai-coding","software-development","startup","product-management","agentic-ai","business-strategy","platform","democratization","tech-trends"],"normalizedKeywords":["엔지니어링","비즈니스·전략","기술 트렌드"],"targetAudience":[{"who":"초기 창업자","why":"AI로 소프트웨어가 민주화될 때 스타트업 기회가 어떻게 커지는지 이해하는 데 유용하다."},{"who":"프로덕트 매니저","why":"모델 성능이 좋아질수록 제품 설계와 하니스, 멀티에이전트 경험이 왜 중요해지는지 볼 수 있다."},{"who":"개발자","why":"코딩 자동화가 개발 방식과 협업 구조를 어떻게 바꾸는지 직접적인 시사점을 준다."}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","엔지니어·개발자"],"summary":"이 영상은 AI가 코딩의 비용을 극적으로 낮추면서 소프트웨어 제작이 더 이상 소수의 엔지니어만의 일이 아니게 된다고 말한다. Boris Cherny는 누구나 코드를 쓸 수 있는 시대가 오면 스위칭 비용이나 프로세스 우위 같은 기존 해자는 약해지지만, 네트워크 효과와 규모, 자원 같은 플랫폼 해자는 여전히 중요하다고 본다.\n\n또한 AI 네이티브로 출발하는 스타트업은 대기업보다 훨씬 빠르게 실험하고 확장할 수 있어, 앞으로 10년은 큰 disruption이 많이 나오는 시기라고 전망한다. 대화 후반부에서는 Claude Code의 성공이 모델 성능과 제품 설계의 혼합 결과라는 점, 그리고 멀티에이전트·루프·하니스 설계처럼 모델을 잘 쓰게 만드는 제품 경험이 당분간 중요하다는 점을 강조한다.","insights":["코딩이 싸질수록 해자는 기술보다 플랫폼 구조로 이동한다.","스위칭 비용과 프로세스 파워는 AI에 의해 약해진다.","새로 시작하는 스타트업은 AI를 처음부터 내장해 대기업보다 유리하다.","제품 성공은 모델 성능만이 아니라 사람들에게 사랑받는 경험에 달려 있다.","AI가 좋아질수록 하니스는 덜 중요해지고 멀티에이전트 설계가 중요해진다."],"keyClips":[{"clipId":"SlGRN8jh2RI:c1:1-3","startSegmentIndex":1,"endSegmentIndex":3,"startTime":600.31,"endTime":623.84,"durationSeconds":23.5,"preview":"전원 코딩하는 조직","mustSee":false},{"clipId":"SlGRN8jh2RI:c1:13-24","startSegmentIndex":13,"endSegmentIndex":24,"startTime":683.76,"endTime":775.04,"durationSeconds":91.3,"preview":"AI가 바꾸는 해자","mustSee":true},{"clipId":"SlGRN8jh2RI:c1:32-40","startSegmentIndex":32,"endSegmentIndex":40,"startTime":833.72,"endTime":897.35,"durationSeconds":63.6,"preview":"사랑받는 제품의 법칙","mustSee":false},{"clipId":"SlGRN8jh2RI:c1:42-61","startSegmentIndex":42,"endSegmentIndex":61,"startTime":901.28,"endTime":1044.669,"durationSeconds":143.4,"preview":"소프트웨어의 대중화","mustSee":true},{"clipId":"SlGRN8jh2RI:c1:65-76","startSegmentIndex":65,"endSegmentIndex":76,"startTime":1064.04,"endTime":1146.6,"durationSeconds":82.6,"preview":"내부 도구의 격차","mustSee":true},{"clipId":"SlGRN8jh2RI:c1:78-84","startSegmentIndex":78,"endSegmentIndex":84,"startTime":1152.159,"endTime":1209.4,"durationSeconds":57.2,"preview":"멀티에이전트 설계","mustSee":false}],"curatedSegments":[{"segmentIndex":43,"text":"So, we don't have to do type ahead anymore, we can just have the agent write all of the code.","startTime":234.92000000000002,"endTime":240.8,"durationSeconds":6,"level":"B2","overallScore":8,"rationale":"패러다임 전환을 압축해 말한 핵심 주장."},{"segmentIndex":50,"text":"But essentially, we were trying to build this thing that was like pre-PMF, and we knew that it wouldn't have PMF for 6 months because we were building for the next model.","startTime":276.88,"endTime":283.96,"durationSeconds":7,"level":"C1","overallScore":8,"rationale":"미래 모델을 선행해 제품화한 통찰이 큼."},{"segmentIndex":16,"text":"So, I think like by a couple years from now, the model is just going to be doing all the code. It's going to be starting the agents. It's going to be building the environments.","startTime":1296.16,"endTime":1302.16,"durationSeconds":6,"level":"B2","overallScore":7.6,"rationale":"미래상 예측이 강하고 명확함."},{"segmentIndex":38,"text":"Uh there's this idea that the model can do all the stuff that no product has yet captured.","startTime":210.96,"endTime":215.64,"durationSeconds":5,"level":"C1","overallScore":7,"rationale":"모델 능력과 제품화 간 격차를 통찰적으로 설명."},{"segmentIndex":42,"text":"But the feeling was we could actually go a lot further than that. And the model was almost ready for the next big step.","startTime":229.16,"endTime":234.92000000000002,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"기술 가능성 판단이 드러나는 핵심 문장."},{"segmentIndex":58,"text":"Uh if this is one of the three best from Anthropic, can you tell us more about what you mean by that, and what might still not be solved, or what second-order problems might come?","startTime":312.28,"endTime":320.44,"durationSeconds":8,"level":"C1","overallScore":7.2,"rationale":"핵심 주장과 후속 문제를 깊게 여는 질문."},{"segmentIndex":71,"text":"I was just trying to kind of push to see how far I can get it. Um but yeah, it's like for me it's just solved. Um but this is not the case everywhere. There's very big complicated code bases.","startTime":392.4,"endTime":398.15999999999997,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"개인 판단과 한계 인식이 함께 담김."},{"segmentIndex":91,"text":"And at [snorts] this point, I have like dozens of loops that are running for stuff. So, I have one that's babysitting my PRs, like fixing CI, auto-rebasing.","startTime":495.64,"endTime":498.84,"durationSeconds":3,"level":"C1","overallScore":7.2,"rationale":"구체 사례와 생생한 표현이 풍부하다."},{"segmentIndex":96,"text":"I sort of feel like loops are the future at this point. If you haven't experimented with it, highly recommend it.","startTime":517.08,"endTime":522.24,"durationSeconds":5,"level":"B2","overallScore":7,"rationale":"의견과 권유가 분명해 학습가치 높다."},{"segmentIndex":102,"text":"I feel like the way that things are going is generally there's going to be a lot more generalists than there are today.","startTime":552.84,"endTime":560.4,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"미래 인력 구조에 대한 핵심 전망이다."},{"segmentIndex":106,"text":"But I think the thing that we're going to start to see a lot more of is generalists that are cross-disciplinary.","startTime":575.28,"endTime":580.72,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"미래 변화 방향을 압축해 제시한다."},{"segmentIndex":61,"text":"It's knowing the domain that's the hard part.","startTime":1035.56,"endTime":1044.669,"durationSeconds":9,"level":"B2","overallScore":6.4,"rationale":"핵심 원리를 짚는 짧은 통찰."},{"segmentIndex":69,"text":"I think on the product side, there's probably a far larger gap. And that's just related to us changing all of our processes.","startTime":1090.36,"endTime":1096.56,"durationSeconds":6,"level":"B2","overallScore":6.8,"rationale":"제품 격차의 원인을 짚는 문장."},{"segmentIndex":71,"text":"And our Claudes are talking all day like as I'm coding, as my Claudes are coding in a loop, they will communicate over Slack to talk to other people's Claudes that are also running in a loop to kind of figure out unknowns.","startTime":1100.12,"endTime":1110.88,"durationSeconds":11,"level":"C1","overallScore":7.2,"rationale":"작업 방식 묘사와 표현 모두 풍부."},{"segmentIndex":72,"text":"We have no more manually written code anywhere at the company.","startTime":1110.88,"endTime":1113.96,"durationSeconds":3,"level":"B2","overallScore":6.4,"rationale":"강한 주장으로 조직 변화를 보여줌."},{"segmentIndex":5,"text":"And then it uses the Slack MCP to do that. So, so I think actually over time, it's not on users to figure out how to hold the tools better.","startTime":1221.52,"endTime":1228.48,"durationSeconds":7,"level":"B2","overallScore":7,"rationale":"책임 주체에 대한 관점 제시."},{"segmentIndex":6,"text":"And if that's the case, it's actually a product design problem and like I'm not doing a good job.","startTime":1228.48,"endTime":1232.52,"durationSeconds":4,"level":"B2","overallScore":7,"rationale":"문제 원인 재정의가 분명함."},{"segmentIndex":7,"text":"It's really on the model to do this stuff better and on us kind of prompting it so it naturally does this.","startTime":1232.52,"endTime":1243.31,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"역할 분담에 대한 핵심 주장."},{"segmentIndex":14,"text":"I think maybe like kind of the most fundamental way to answer that is it doesn't matter.","startTime":1288.6,"endTime":1293,"durationSeconds":4,"level":"B1","overallScore":6.6,"rationale":"핵심 입장을 압축해 보여줌."},{"segmentIndex":18,"text":"These I don't think these will be decisions that we are making as engineers anymore.","startTime":1306.64,"endTime":1311.16,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"엔지니어 역할 변화 통찰 제시."}],"generatedAt":"2026-06-25T00:03:37.212Z","keyClipsTotalSec":746},{"videoId":"SlGRN8jh2RI","chunkIndex":2,"totalChunks":3,"title":"Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next — Part 3 of 3","thumbnail":"https://i.ytimg.com/vi/SlGRN8jh2RI/maxresdefault.jpg","duration":1476,"uploader":"Sequoia Capital","youtubeUrl":"https://www.youtube.com/watch?v=SlGRN8jh2RI","keywords":["ai-agents","mcp","computer-use","coding-assistance","product-design","cloud-computing","local-models","workflow-automation"],"normalizedKeywords":["엔지니어링","프로덕트","기술 트렌드"],"targetAudience":[{"who":"엔지니어","why":"AI 에이전트, MCP, computer use를 어떤 방식으로 붙일지 감을 잡을 수 있음"},{"who":"프로덕트 매니저","why":"모델이 더 똑똑해질 때 제품 설계를 어떻게 해야 하는지 힌트를 얻을 수 있음"},{"who":"지식노동자","why":"클라우드 도구와 로컬 도구를 AI가 어떻게 연결해 쓰는지 이해하는 데 유용함"}],"normalizedAudience":["엔지니어·개발자","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 구간은 AI 모델이 점점 더 스스로 도구 사용 방식을 찾아가게 되면서, 인간이 세세한 워크플로우를 설계하는 시대가 끝나가고 있다고 본다. Boris는 모델이 점점 더 loop, batch, 에이전트 실행, 환경 구성까지 알아서 처리하게 되며, 클라우드냐 로컬이냐 같은 선택도 결국 모델이 상황에 맞게 결정할 문제라고 말한다.\n\n또한 일반 지식노동 영역에서는 MCP가 핵심 연결 방식이라고 강조한다. Salesforce, Google Docs, Calendar 같은 도구는 MCP로 붙이고, 없는 시스템은 computer use가 보완하는 구조이며, 모델 입장에서는 결국 모든 것이 토큰으로 보이기 때문에 구체적 통합 방식 자체는 덜 중요하다는 메시지를 전한다.","insights":["도구 선택의 주체는 점점 인간이 아니라 모델이 된다.","좋은 제품은 사용법을 가르치기보다 자연스런 행동을 유도한다.","MCP는 지식노동 AI의 범용 연결 계층이 될 수 있다.","computer use는 느려도 '마지막 연결고리' 역할을 한다.","모델은 API든 앱이든 결국 토큰으로만 취급한다."],"keyClips":[{"clipId":"SlGRN8jh2RI:c2:1-7","startSegmentIndex":1,"endSegmentIndex":7,"startTime":1201.15,"endTime":1243.31,"durationSeconds":42.2,"preview":"모델이 스스로 배운다","mustSee":false},{"clipId":"SlGRN8jh2RI:c2:8-18","startSegmentIndex":8,"endSegmentIndex":18,"startTime":1243.31,"endTime":1311.16,"durationSeconds":67.9,"preview":"클라우드냐 로컬냐","mustSee":true},{"clipId":"SlGRN8jh2RI:c2:20-28","startSegmentIndex":20,"endSegmentIndex":28,"startTime":1317.76,"endTime":1376.47,"durationSeconds":58.7,"preview":"MCP가 답이다","mustSee":true},{"clipId":"SlGRN8jh2RI:c2:29-35","startSegmentIndex":29,"endSegmentIndex":35,"startTime":1376.47,"endTime":1415.48,"durationSeconds":39,"preview":"컴퓨터 사용의 의미","mustSee":false},{"clipId":"SlGRN8jh2RI:c2:38-42","startSegmentIndex":38,"endSegmentIndex":42,"startTime":1425.28,"endTime":1466.8,"durationSeconds":41.5,"preview":"미래형 제품의 형태","mustSee":true}],"curatedSegments":[{"segmentIndex":43,"text":"So, we don't have to do type ahead anymore, we can just have the agent write all of the code.","startTime":234.92000000000002,"endTime":240.8,"durationSeconds":6,"level":"B2","overallScore":8,"rationale":"패러다임 전환을 압축해 말한 핵심 주장."},{"segmentIndex":50,"text":"But essentially, we were trying to build this thing that was like pre-PMF, and we knew that it wouldn't have PMF for 6 months because we were building for the next model.","startTime":276.88,"endTime":283.96,"durationSeconds":7,"level":"C1","overallScore":8,"rationale":"미래 모델을 선행해 제품화한 통찰이 큼."},{"segmentIndex":16,"text":"So, I think like by a couple years from now, the model is just going to be doing all the code. It's going to be starting the agents. It's going to be building the environments.","startTime":1296.16,"endTime":1302.16,"durationSeconds":6,"level":"B2","overallScore":7.6,"rationale":"미래상 예측이 강하고 명확함."},{"segmentIndex":38,"text":"Uh there's this idea that the model can do all the stuff that no product has yet captured.","startTime":210.96,"endTime":215.64,"durationSeconds":5,"level":"C1","overallScore":7,"rationale":"모델 능력과 제품화 간 격차를 통찰적으로 설명."},{"segmentIndex":42,"text":"But the feeling was we could actually go a lot further than that. And the model was almost ready for the next big step.","startTime":229.16,"endTime":234.92000000000002,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"기술 가능성 판단이 드러나는 핵심 문장."},{"segmentIndex":58,"text":"Uh if this is one of the three best from Anthropic, can you tell us more about what you mean by that, and what might still not be solved, or what second-order problems might come?","startTime":312.28,"endTime":320.44,"durationSeconds":8,"level":"C1","overallScore":7.2,"rationale":"핵심 주장과 후속 문제를 깊게 여는 질문."},{"segmentIndex":71,"text":"I was just trying to kind of push to see how far I can get it. Um but yeah, it's like for me it's just solved. Um but this is not the case everywhere. There's very big complicated code bases.","startTime":392.4,"endTime":398.15999999999997,"durationSeconds":6,"level":"B2","overallScore":7,"rationale":"개인 판단과 한계 인식이 함께 담김."},{"segmentIndex":91,"text":"And at [snorts] this point, I have like dozens of loops that are running for stuff. So, I have one that's babysitting my PRs, like fixing CI, auto-rebasing.","startTime":495.64,"endTime":498.84,"durationSeconds":3,"level":"C1","overallScore":7.2,"rationale":"구체 사례와 생생한 표현이 풍부하다."},{"segmentIndex":96,"text":"I sort of feel like loops are the future at this point. If you haven't experimented with it, highly recommend it.","startTime":517.08,"endTime":522.24,"durationSeconds":5,"level":"B2","overallScore":7,"rationale":"의견과 권유가 분명해 학습가치 높다."},{"segmentIndex":102,"text":"I feel like the way that things are going is generally there's going to be a lot more generalists than there are today.","startTime":552.84,"endTime":560.4,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"미래 인력 구조에 대한 핵심 전망이다."},{"segmentIndex":106,"text":"But I think the thing that we're going to start to see a lot more of is generalists that are cross-disciplinary.","startTime":575.28,"endTime":580.72,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"미래 변화 방향을 압축해 제시한다."},{"segmentIndex":61,"text":"It's knowing the domain that's the hard part.","startTime":1035.56,"endTime":1044.669,"durationSeconds":9,"level":"B2","overallScore":6.4,"rationale":"핵심 원리를 짚는 짧은 통찰."},{"segmentIndex":69,"text":"I think on the product side, there's probably a far larger gap. And that's just related to us changing all of our processes.","startTime":1090.36,"endTime":1096.56,"durationSeconds":6,"level":"B2","overallScore":6.8,"rationale":"제품 격차의 원인을 짚는 문장."},{"segmentIndex":71,"text":"And our Claudes are talking all day like as I'm coding, as my Claudes are coding in a loop, they will communicate over Slack to talk to other people's Claudes that are also running in a loop to kind of figure out unknowns.","startTime":1100.12,"endTime":1110.88,"durationSeconds":11,"level":"C1","overallScore":7.2,"rationale":"작업 방식 묘사와 표현 모두 풍부."},{"segmentIndex":72,"text":"We have no more manually written code anywhere at the company.","startTime":1110.88,"endTime":1113.96,"durationSeconds":3,"level":"B2","overallScore":6.4,"rationale":"강한 주장으로 조직 변화를 보여줌."},{"segmentIndex":5,"text":"And then it uses the Slack MCP to do that. So, so I think actually over time, it's not on users to figure out how to hold the tools better.","startTime":1221.52,"endTime":1228.48,"durationSeconds":7,"level":"B2","overallScore":7,"rationale":"책임 주체에 대한 관점 제시."},{"segmentIndex":6,"text":"And if that's the case, it's actually a product design problem and like I'm not doing a good job.","startTime":1228.48,"endTime":1232.52,"durationSeconds":4,"level":"B2","overallScore":7,"rationale":"문제 원인 재정의가 분명함."},{"segmentIndex":7,"text":"It's really on the model to do this stuff better and on us kind of prompting it so it naturally does this.","startTime":1232.52,"endTime":1243.31,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"역할 분담에 대한 핵심 주장."},{"segmentIndex":14,"text":"I think maybe like kind of the most fundamental way to answer that is it doesn't matter.","startTime":1288.6,"endTime":1293,"durationSeconds":4,"level":"B1","overallScore":6.6,"rationale":"핵심 입장을 압축해 보여줌."},{"segmentIndex":18,"text":"These I don't think these will be decisions that we are making as engineers anymore.","startTime":1306.64,"endTime":1311.16,"durationSeconds":5,"level":"B2","overallScore":6.8,"rationale":"엔지니어 역할 변화 통찰 제시."}],"generatedAt":"2026-06-25T00:04:08.098Z","keyClipsTotalSec":746}]}