{"success":true,"count":10,"items":[{"videoId":"Ybrl4FYM57c","chunkIndex":0,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 1 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["artificial-intelligence","software-engineering","engineering-leadership","product-development","developer-tools","productivity","team-culture","ai-coding","technical-management","future-of-work"],"normalizedKeywords":["엔지니어링","리더십·매니지먼트","기술 트렌드"],"targetAudience":[{"who":"엔지니어링 리더","why":"AI로 개발 생산성이 급변할 때 팀 운영과 책임 구조를 다시 설계하는 데 유용함"},{"who":"프로덕트 매니저","why":"코딩 비용이 낮아진 환경에서 검증, 우선순위, 실행 방식이 어떻게 바뀌는지 볼 수 있음"},{"who":"개발자","why":"AI 코딩 시대에 필요한 주도성, 검증 습관, 협업 방식의 변화를 이해할 수 있음"}],"normalizedAudience":["엔지니어·개발자","프로덕트 매니저·기획자"],"summary":"이 영상은 Anthropic의 Fiona Fung이 AI 코딩이 소프트웨어 개발의 병목을 어떻게 바꾸고 있는지, 그리고 그 변화가 팀 운영과 역할 정의를 어떻게 재편하는지 이야기하는 대화의 도입부다. 예전에는 코드를 많이 쓰는 것 자체가 어려웠지만, 이제는 더 많이 쓰는 것보다 무엇을 검증하고 어떤 목표를 세우는지가 더 중요해졌다고 본다. 그래서 고성과 팀은 더 많은 주도성, 더 높은 책임감, 그리고 더 강한 검증 체계를 요구받는다.\n\n동시에 이 변화는 사람 사이의 연결을 약하게 만들 수 있다. 모두가 에이전트와만 일하면 외로워질 수 있으므로, 팀은 pair programming 같은 의도적 협업 장치를 다시 만들어야 한다고 말한다. 전반적으로 이 대화는 'AI를 얼마나 잘 쓰느냐'보다 'AI로 인해 바뀐 환경에서 어떤 태도와 시스템이 필요한가'에 초점을 맞춘다.","insights":["AI가 코딩 병목을 없애면, 문제는 '얼마나'가 아니라 '무엇을'이다.","생산성이 높아질수록 주도성과 책임감이 더 중요해진다.","코드가 쉬워질수록 검증 체계가 팀의 핵심 역량이 된다.","AI 시대에도 협업의 외로움을 줄이는 장치는 여전히 필요하다.","변화가 두렵다면 통제 가능한 행동부터 찾는 태도가 가장 실용적이다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c0:1-7","startSegmentIndex":1,"endSegmentIndex":7,"startTime":1.63,"endTime":33.12,"durationSeconds":31.5,"preview":"AI시대의 새 병목","mustSee":true},{"clipId":"Ybrl4FYM57c:c0:8-13","startSegmentIndex":8,"endSegmentIndex":13,"startTime":33.12,"endTime":60.92,"durationSeconds":27.8,"preview":"혼자 일하는 외로움","mustSee":false},{"clipId":"Ybrl4FYM57c:c0:40-67","startSegmentIndex":40,"endSegmentIndex":67,"startTime":243.44,"endTime":409.84000000000003,"durationSeconds":166.4,"preview":"도구가 바꾼 일하는 법","mustSee":false},{"clipId":"Ybrl4FYM57c:c0:81-96","startSegmentIndex":81,"endSegmentIndex":96,"startTime":496.52,"endTime":608.48,"durationSeconds":112,"preview":"검증이 더 중요해졌다","mustSee":true}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T12:00:00.741Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":1,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 2 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai","product-management","software-engineering","code-review","automation","leadership","developer-tools","tdd","hiring","distributed-systems"],"normalizedKeywords":["엔지니어링","프로덕트","리더십·매니지먼트"],"targetAudience":[{"who":"엔지니어링 리드","why":"AI 도구로 팀의 생산성과 품질을 동시에 관리하는 방법을 배울 수 있음"},{"who":"프로덕트 매니저","why":"피드백과 품질 신호를 제품 개선 루프로 연결하는 운영 방식을 참고할 수 있음"},{"who":"주니어 개발자","why":"AI 시대에 어떤 역량이 중요해지고 어떤 사고방식이 필요한지 감을 잡을 수 있음"}],"normalizedAudience":["엔지니어·개발자","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 영상은 Claude Code와 같은 AI 도구가 제품팀의 일하는 방식을 어떻게 바꾸고 있는지 보여준다. 특히 관리자는 AI를 단순히 PR 생성용이 아니라, 팀이 무엇을 만들었고 어떤 피드백을 받았는지 추적해 대화를 이어가는 관리 도구로 활용한다. 피드백 채널과 코드 리뷰, 루틴 자동화, 테스트 생성까지 AI가 개입하면서 병목이 줄고 품질 관리가 더 체계화되지만, 중요한 영역에서는 여전히 사람의 검증이 필요하다는 점도 강조한다.\n\n또한 이 변화는 채용 기준과 역할 기대치까지 바꾸고 있다. 창의적이고 제품 감각이 있는 빌더와, 복잡한 시스템을 검증할 수 있는 깊은 전문성을 가진 사람이 모두 필요해졌고, AI 덕분에 비전공 영역이나 모바일 같은 다른 표면까지도 더 많은 사람이 도전할 수 있게 됐다. 전체적으로 이 대화는 'AI가 코드를 대신 써준다'보다 'AI가 팀의 야망과 운영 범위를 넓힌다'는 메시지에 가깝다.","insights":["AI는 생산 도구가 아니라 팀 운영의 관측 레이어가 된다.","피드백을 자동 요약하면 관리자는 '무엇을 만들었나'보다 '어떻게 먹혔나'를 본다.","품질은 사람 감각만으로 못 지킨다, 기준을 코드와 스펙에 박아야 한다.","테스트와 코드리뷰 자동화는 TDD와 검증의 진입장벽을 크게 낮춘다.","AI 시대의 핵심 역량은 도구 사용법보다 더 큰 야망을 설계하는 힘이다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c1:2-18","startSegmentIndex":2,"endSegmentIndex":18,"startTime":610.2,"endTime":731.76,"durationSeconds":121.6,"preview":"AI로 팀을 보는 법","mustSee":false},{"clipId":"Ybrl4FYM57c:c1:24-34","startSegmentIndex":24,"endSegmentIndex":34,"startTime":762.28,"endTime":854.68,"durationSeconds":92.4,"preview":"피드백 자동화 루틴","mustSee":false},{"clipId":"Ybrl4FYM57c:c1:37-55","startSegmentIndex":37,"endSegmentIndex":55,"startTime":881.08,"endTime":1016.68,"durationSeconds":135.6,"preview":"코드리뷰와 TDD","mustSee":false},{"clipId":"Ybrl4FYM57c:c1:58-68","startSegmentIndex":58,"endSegmentIndex":68,"startTime":1028.959,"endTime":1099.88,"durationSeconds":70.9,"preview":"채용 기준의 변화","mustSee":false},{"clipId":"Ybrl4FYM57c:c1:71-80","startSegmentIndex":71,"endSegmentIndex":80,"startTime":1109.2,"endTime":1178.84,"durationSeconds":69.6,"preview":"야망의 سق시트","mustSee":true}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T14:57:54.544Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":2,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 3 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["growth-mindset","ai-adoption","small-business","career-growth","fear","learning","entrepreneurship","productivity","storytelling"],"normalizedKeywords":["비즈니스·전략","커리어·성장","기술 트렌드"],"targetAudience":[{"who":"작은 사업자","why":"AI를 실무에 적용해 반복 업무를 줄이고 운영 효율을 높이는 법을 배울 수 있음"},{"who":"커리어 전환자","why":"불확실성 속에서 성장 마인드와 통제 가능한 행동을 찾는 관점을 얻을 수 있음"},{"who":"프로덕트 실무자","why":"사용자 관찰과 피드백을 바탕으로 AI 도구의 실제 활용처를 발견하는 감각을 배울 수 있음"}],"normalizedAudience":["창업자·스타트업","지식노동자 일반","학생·주니어"],"summary":"이 구간의 핵심은 불확실한 시대에 사람과 조직이 어떻게 뒤처지지 않고 성장하느냐이다. Fiona Fung은 성장 마인드셋, 즉 '항상 배우고 변화해야 한다'는 태도가 커리어와 삶 전반에서 가장 중요한 기반이라고 말한다. 성공을 만든 습관이 오히려 다음 성장 단계에서는 장애물이 될 수 있으니, 두려움을 느끼더라도 내가 통제할 수 있는 행동을 찾아 작게라도 움직여야 한다고 조언한다.\n\n이후 화제는 AI 활용 격차로 넘어가며, 그녀는 작은 사업자들이 실제로 가장 싫어하는 반복 업무를 AI가 크게 줄여줄 수 있다고 설명한다. 자신의 경험과 주변 소상공인 사례를 통해, AI는 거창한 기술이 아니라 문서 정리·비용 처리·메뉴 검색·비교 분석처럼 즉시 체감되는 문제를 풀 때 가장 빠르게 확산된다고 강조한다.","insights":["성장은 익숙한 방식을 버릴 때 시작된다.","두려움은 사라지기보다 통제 가능한 행동으로 바꿔야 한다.","불확실성은 '나에게 일어나는 일'이 아니라 '내가 바꿀 일'로 재정의해야 한다.","AI 격차는 기술이 아니라 실제 업무 문제를 누가 먼저 푸느냐의 차이다.","가장 잘 퍼지는 AI는 멋진 기능보다 귀찮은 반복 일을 없애는 도구다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c2:2-19","startSegmentIndex":2,"endSegmentIndex":19,"startTime":1204.4,"endTime":1324.28,"durationSeconds":119.9,"preview":"성장 마인드셋의 힘","mustSee":false},{"clipId":"Ybrl4FYM57c:c2:20-44","startSegmentIndex":20,"endSegmentIndex":44,"startTime":1324.28,"endTime":1553.2,"durationSeconds":228.9,"preview":"두려움을 넘는 선택","mustSee":false},{"clipId":"Ybrl4FYM57c:c2:45-80","startSegmentIndex":45,"endSegmentIndex":80,"startTime":1553.2,"endTime":1788.68,"durationSeconds":235.5,"preview":"작은 사업과 AI","mustSee":true},{"clipId":"Ybrl4FYM57c:c2:81-84","startSegmentIndex":81,"endSegmentIndex":84,"startTime":1788.68,"endTime":1809.28,"durationSeconds":20.6,"preview":"AI를 퍼뜨리는 법","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T14:58:28.288Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":3,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 4 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai","productivity","agents","asynchronous-work","product-management","engineering","automation","latent-demand","knowledge-work","agency"],"normalizedKeywords":["프로덕트","엔지니어링","리더십·매니지먼트"],"targetAudience":[{"who":"프로덕트 매니저","why":"사용자 행동에서 잠재 수요를 읽고 제품을 확장하는 방법을 배울 수 있음"},{"who":"엔지니어","why":"비동기 에이전트와 루틴 기반 업무 방식의 변화를 이해하는 데 도움됨"},{"who":"지식노동자","why":"AI를 일상 업무에 적용하고 자동화하는 실전 감각을 얻을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자","지식노동자 일반"],"summary":"이 구간은 AI 도구를 어떻게 더 많은 사람에게 유용하게 만들지, 그리고 제품팀이 어떤 방식으로 새로운 기회를 포착하는지를 중심으로 전개된다. 화자는 주변 사람들에게 실제 사용 사례를 보여주며 대화를 시작하는 것이 AI 격차를 줄이는 가장 좋은 방법이라고 말하고, Anthropic이 코딩과 지식노동에서 잠재 수요를 빠르게 발견해 제품화해온 방식을 설명한다.\n\n후반부에서는 엔지니어링의 다음 변화가 '동기식 작업'에서 '비동기식 작업'으로 이동하는 것이라고 보고, 루틴이 에이전트를 대신 띄우고 PR까지 생성하는 미래를 예시로 든다. 이때 팀에서 중요한 덕목으로는 높은 자율성(agency)과 높은 책임감(accountability)의 균형이 제시되며, 결국 AI 활용도는 비용을 태우는 양보다 실제 ROI를 얼마나 만드는지로 평가해야 한다는 분위기로 마무리된다.","insights":["AI 확산은 기능보다 '사용 사례 공유'에서 시작된다.","사용자가 우회하는 지점이 곧 잠재 수요의 신호다.","엔지니어링은 동기식 실행보다 비동기 오케스트레이션으로 간다.","자율성은 책임감이 붙을 때만 생산성이 된다.","AI 활용은 토큰 사용량보다 실제 ROI로 평가해야 한다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c3:3-16","startSegmentIndex":3,"endSegmentIndex":16,"startTime":1807.64,"endTime":1907.6,"durationSeconds":100,"preview":"작은 사용례가 확산을 만든다","mustSee":false},{"clipId":"Ybrl4FYM57c:c3:17-35","startSegmentIndex":17,"endSegmentIndex":35,"startTime":1907.6,"endTime":2080.28,"durationSeconds":172.7,"preview":"잠재수요를 읽는 법","mustSee":false},{"clipId":"Ybrl4FYM57c:c3:41-65","startSegmentIndex":41,"endSegmentIndex":65,"startTime":2116.04,"endTime":2287.6,"durationSeconds":171.6,"preview":"비동기 에이전트의 시대","mustSee":true},{"clipId":"Ybrl4FYM57c:c3:68-80","startSegmentIndex":68,"endSegmentIndex":80,"startTime":2301.56,"endTime":2402.04,"durationSeconds":100.5,"preview":"자율성과 책임의 균형","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T14:58:59.033Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":4,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 5 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai-productivity","engineering-management","metrics","quality-assurance","evaluations","leadership","productivity","developer-experience","ai-tools"],"normalizedKeywords":["리더십·매니지먼트","엔지니어링","프로덕트"],"targetAudience":[{"who":"엔지니어링 리더","why":"AI 도입 효과를 숫자와 대화로 함께 관리하는 법을 배울 수 있음"},{"who":"프로덕트 매니저","why":"성과 지표를 행동이 아닌 실제 결과로 설계하는 관점을 얻을 수 있음"},{"who":"개발팀 실무자","why":"빠른 코드 생산 속도 속에서 품질과 사용자 불만을 잡는 방법이 유용함"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자"],"summary":"이 구간은 AI 도구와 자동화가 늘어난 환경에서 엔지니어 생산성과 팀 품질을 어떻게 봐야 하는지에 대한 Fiona Fung의 실전 관점을 다룬다. 그녀는 lines of code, token usage, PR 수 같은 지표가 쉽게 '행동'만 측정하게 만들며, 결국 중요한 것은 얼마나 많은 코드를 썼느냐가 아니라 실제로 어떤 결과를 만들었는지라고 강조한다. Facebook Marketplace 사례를 들어, 숫자가 좋아 보여도 실제 목표와 어긋날 수 있고, 그래서 지표는 언제든 다시 정의되어야 한다고 설명한다.\n\n후반부에서는 품질을 지키는 방법으로 사후 리뷰보다 테스트·모니터링·evals 같은 선제적 장치를 더 강화해야 한다고 말한다. 특히 'bad'와 'sad' 같은 체계를 만들어 서비스별로 심각도 기준을 명확히 하고, 사용자 불만을 반영하는 신호까지 추적하는 방식이 인상적이다. 마지막에는 관리자도 IC를 병행하는 player-coach 모델까지 언급되며, AI 시대의 팀 운영은 단순한 관리보다 현장 감각과 학습 루프를 유지하는 구조가 중요하다는 메시지로 이어진다.","insights":["생산성 지표는 행동이 아니라 결과에 연결돼야 한다.","코드량·토큰량은 쉽게 왜곡되므로 목적을 먼저 봐야 한다.","좋은 메트릭도 목표를 벗어나면 즉시 재설계해야 한다.","품질은 사후 리뷰보다 테스트·모니터링으로 먼저 잡는다.","사용자 불만 신호까지 봐야 진짜 경험 품질이 보인다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c4:4-15","startSegmentIndex":4,"endSegmentIndex":15,"startTime":2427.72,"endTime":2516.28,"durationSeconds":88.6,"preview":"지표보다 결과","mustSee":true},{"clipId":"Ybrl4FYM57c:c4:16-28","startSegmentIndex":16,"endSegmentIndex":28,"startTime":2516.28,"endTime":2663.92,"durationSeconds":147.6,"preview":"메트릭의 함정","mustSee":false},{"clipId":"Ybrl4FYM57c:c4:33-42","startSegmentIndex":33,"endSegmentIndex":42,"startTime":2687.36,"endTime":2772.92,"durationSeconds":85.6,"preview":"품질은 선제 대응","mustSee":false},{"clipId":"Ybrl4FYM57c:c4:45-60","startSegmentIndex":45,"endSegmentIndex":60,"startTime":2783.84,"endTime":2902.12,"durationSeconds":118.3,"preview":"불만도 데이터다","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T14:59:30.155Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":5,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 6 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai","engineering","leadership","product-development","coding-workflow","pair-programming","developer-tools","management","software-craft","team-culture"],"normalizedKeywords":["리더십·매니지먼트","엔지니어링","기술 트렌드"],"targetAudience":[{"who":"엔지니어 리더","why":"AI 도구가 개발과 관리 방식을 어떻게 바꾸는지 실무적으로 볼 수 있음"},{"who":"매니저","why":"새 팀에 합류할 때 먼저 배우고 들어가는 리더십 원칙을 얻을 수 있음"},{"who":"개발자","why":"AI 시대에 코딩 감각과 제품 감각을 유지하는 방법을 배울 수 있음"}],"normalizedAudience":["엔지니어·개발자","지식노동자 일반"],"summary":"이 영상은 AI 도구, 특히 Claude Code가 엔지니어의 일 방식과 리더의 역할을 어떻게 바꾸는지에 대한 Fiona Fung의 관점을 담고 있다. 그는 새 팀에 합류한 리더가 곧바로 관리 모드로 들어가기보다, 먼저 IC처럼 제품과 코드베이스를 깊게 익혀야 팀과의 신뢰가 생긴다고 말한다. 또한 리더가 매일 직접 제품을 써야 현장감과 사용자 감각을 잃지 않는다고 강조한다.\n\n후반부에서는 AI 코딩 환경이 가져온 변화와 부작용도 다룬다. 에이전트와 함께 일하는 시간이 길어지며 개발이 다소 외로워질 수 있고, 예전처럼 혼자 몰입해 코딩하며 느끼던 'flow'와 완성의 쾌감이 줄어들 수 있다는 점이다. 이를 보완하기 위해 팀은 pairwise programming lunch와 해커톤 같은 공동 작업을 통해 서로의 방식을 배우고 연결을 유지하려고 한다.","insights":["리더는 먼저 배우는 사람으로 들어가야 신뢰가 생긴다.","제품을 매일 써야 숫자보다 실제 감각을 잃지 않는다.","AI가 코딩을 대체해도 아키텍처 이해는 여전히 중요하다.","에이전트 시대엔 혼자보다 함께 일하는 장치가 필요하다.","워크플로 최적화는 정답보다 실험의 문제다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c5:3-18","startSegmentIndex":3,"endSegmentIndex":18,"startTime":3010.12,"endTime":3141.8,"durationSeconds":131.7,"preview":"리더는 먼저 배워라","mustSee":false},{"clipId":"Ybrl4FYM57c:c5:19-24","startSegmentIndex":19,"endSegmentIndex":24,"startTime":3141.8,"endTime":3170.32,"durationSeconds":28.5,"preview":"직접 써야 보인다","mustSee":false},{"clipId":"Ybrl4FYM57c:c5:25-42","startSegmentIndex":25,"endSegmentIndex":42,"startTime":3170.32,"endTime":3309.52,"durationSeconds":139.2,"preview":"AI로 다시 코딩","mustSee":true},{"clipId":"Ybrl4FYM57c:c5:43-54","startSegmentIndex":43,"endSegmentIndex":54,"startTime":3309.52,"endTime":3395.2,"durationSeconds":85.7,"preview":"코드는 줄고 이해는 남는다","mustSee":false},{"clipId":"Ybrl4FYM57c:c5:55-68","startSegmentIndex":55,"endSegmentIndex":68,"startTime":3395.2,"endTime":3485.92,"durationSeconds":90.7,"preview":"혼자보다 같이","mustSee":false},{"clipId":"Ybrl4FYM57c:c5:69-82","startSegmentIndex":69,"endSegmentIndex":82,"startTime":3485.92,"endTime":3600.84,"durationSeconds":114.9,"preview":"최적화의 함정","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T14:59:41.296Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":6,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 7 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai","product-management","engineering","leadership","dogfooding","workflow-automation","data-science","cross-functional","product-sense"],"normalizedKeywords":["리더십·매니지먼트","프로덕트","기술 트렌드"],"targetAudience":[{"who":"엔지니어링 리더","why":"AI로 바뀐 팀 운영 기준과 기대치를 직접 다룬다"},{"who":"프로덕트 매니저","why":"PM 역할의 변화와 제품 감각의 중요성을 배울 수 있다"},{"who":"제품 조직 리더","why":"도그푸딩, 검증, 역할 블러링 같은 운영 원칙이 핵심이다"}],"normalizedAudience":["엔지니어·개발자","프로덕트 매니저·기획자"],"summary":"이 대화는 AI가 제품 조직의 역할 경계를 어떻게 빠르게 바꾸고 있는지에 초점을 맞춘다. 엔지니어는 더 제품 중심적으로, PM은 엔지니어링에 더 가까워지고, 데이터 사이언스나 디자인 같은 주변 직무도 AI로 인해 재편되고 있다는 점을 강조한다. 동시에 이런 변화가 빨라질수록 자동화된 검증과 교차 검토의 중요성도 커진다고 본다.\n\n또 하나의 핵심 축은 '도그푸딩'이다. 화자는 리더일수록 제품을 직접 써야 숨은 문제와 실제 사용 맥락을 놓치지 않는다고 말하며, 데이터만 보지 말고 직접 겪은 사례와 고객 피드백을 함께 보라고 조언한다. 마지막으로 iOS/Android 조직 분리, 자동 리뷰의 범위, 역할 블러링 속 생산성 균형 같은 아직 해결되지 않은 운영 질문들을 남기며, 지금은 조직 설계 자체가 다시 실험 단계에 들어갔다고 정리한다.","insights":["AI는 직무를 대체하기보다 역할 경계를 먼저 무너뜨린다.","엔지니어는 더 제품적으로, PM은 더 기술적으로 변한다.","도그푸딩은 제품의 숨은 결함을 가장 빨리 드러낸다.","데이터보다 현장 사례가 더 먼저 경고를 줄 때가 있다.","자동화가 늘수록 검증 책임은 오히려 더 중요해진다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c6:4-10","startSegmentIndex":4,"endSegmentIndex":10,"startTime":3623,"endTime":3680.52,"durationSeconds":57.5,"preview":"역할 경계의 붕괴","mustSee":false},{"clipId":"Ybrl4FYM57c:c6:12-14","startSegmentIndex":12,"endSegmentIndex":14,"startTime":3686.56,"endTime":3715.92,"durationSeconds":29.4,"preview":"데이터 사이언스의 변화","mustSee":false},{"clipId":"Ybrl4FYM57c:c6:19-24","startSegmentIndex":19,"endSegmentIndex":24,"startTime":3741.84,"endTime":3803.48,"durationSeconds":61.6,"preview":"엔지니어의 새 기준","mustSee":false},{"clipId":"Ybrl4FYM57c:c6:28-45","startSegmentIndex":28,"endSegmentIndex":45,"startTime":3819.349,"endTime":4019.44,"durationSeconds":200.1,"preview":"제품을 직접 써라","mustSee":true},{"clipId":"Ybrl4FYM57c:c6:49-60","startSegmentIndex":49,"endSegmentIndex":60,"startTime":4042.4,"endTime":4115.12,"durationSeconds":72.7,"preview":"현장 피드백의 힘","mustSee":false},{"clipId":"Ybrl4FYM57c:c6:61-72","startSegmentIndex":61,"endSegmentIndex":72,"startTime":4115.12,"endTime":4207.48,"durationSeconds":92.4,"preview":"아직 안 풀린 질문","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T15:00:25.738Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":7,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 8 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["ai-tools","software-engineering","product-development","verification","async-work","engineering-culture","hiring","career-growth","abstraction","product-design"],"normalizedKeywords":["엔지니어링","프로덕트","커리어·성장"],"targetAudience":[{"who":"엔지니어","why":"AI 도구로 바뀌는 개발 방식과 검증, 학습 구조를 이해하는 데 유용함"},{"who":"프로덕트 매니저","why":"경험 품질, 검증 방식, 비동기 협업의 비용을 제품 관점에서 볼 수 있음"},{"who":"주니어 개발자","why":"AI 시대에 무엇을 배워야 하는지와 성장 경로가 어떻게 바뀌는지 힌트를 얻을 수 있음"}],"normalizedAudience":["엔지니어·개발자","프로덕트 매니저·기획자","학생·주니어"],"summary":"이 대화는 AI 도구가 소프트웨어 개발과 제품 제작 방식을 어떻게 바꾸고 있는지에 대한 실무적 고민을 중심으로 전개된다. 특히 단순한 정확도보다도 '좋은 경험'을 어떻게 검증할지, 그리고 비동기 에이전트가 늘어난 환경에서 생기는 컨텍스트 스위칭 비용을 어떻게 줄일지가 핵심 주제다. 화자는 AI가 엔지니어 수요를 줄이기보다 오히려 더 많은 엔지니어링 수요와 새로운 협업 방식을 만들고 있다고 본다.\n\n또한 다음 세대 엔지니어를 어떻게 키울 것인지, 코드를 오래 치는 경험 없이도 기초를 어떻게 익히게 할지에 대한 고민도 나온다. 마지막으로는 빠른 성장 속에서 팀 문화가 흔들리지 않게 지키는 일이 가장 큰 걱정이라고 말하며, 문화는 문구가 아니라 실제 상호작용 속에서 유지되어야 한다는 점을 강조한다.","insights":["AI 시대의 검증은 정확도보다 경험 품질까지 봐야 한다.","비동기 작업이 늘수록 컨텍스트 스위칭 비용도 함께 커진다.","AI는 엔지니어를 덜 필요하게 만들기보다 역할을 더 재편한다.","다음 세대는 코딩량보다 핵심 원리 이해를 더 빨리 배워야 한다.","빠른 성장기에는 문화가 가장 먼저 흔들리는 운영 리스크다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c7:1-8","startSegmentIndex":1,"endSegmentIndex":8,"startTime":4201.23,"endTime":4263.52,"durationSeconds":62.3,"preview":"검증은 경험까지","mustSee":false},{"clipId":"Ybrl4FYM57c:c7:9-21","startSegmentIndex":9,"endSegmentIndex":21,"startTime":4263.52,"endTime":4369.04,"durationSeconds":105.5,"preview":"비동기 피로의 비용","mustSee":true},{"clipId":"Ybrl4FYM57c:c7:22-27","startSegmentIndex":22,"endSegmentIndex":27,"startTime":4369.04,"endTime":4400.24,"durationSeconds":31.2,"preview":"AI가 바꾸는 채용","mustSee":false},{"clipId":"Ybrl4FYM57c:c7:28-46","startSegmentIndex":28,"endSegmentIndex":46,"startTime":4400.24,"endTime":4562.72,"durationSeconds":162.5,"preview":"주니어 성장의 재설계","mustSee":false},{"clipId":"Ybrl4FYM57c:c7:47-65","startSegmentIndex":47,"endSegmentIndex":65,"startTime":4562.72,"endTime":4679.52,"durationSeconds":116.8,"preview":"급진적 추상화의 시대","mustSee":true},{"clipId":"Ybrl4FYM57c:c7:66-73","startSegmentIndex":66,"endSegmentIndex":73,"startTime":4679.52,"endTime":4799.12,"durationSeconds":119.6,"preview":"성장의 마지막 숙제","mustSee":true}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T15:00:48.333Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":8,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 9 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["leadership","management","company-culture","planning","process-automation","productivity","startup","work-culture","decision-making","books"],"normalizedKeywords":["리더십·매니지먼트","비즈니스·전략","커리어·성장"],"targetAudience":[{"who":"팀 리더","why":"빠르게 변하는 조직에서 문화와 실행 방식을 어떻게 유지할지 배울 수 있음"},{"who":"프로덕트 매니저","why":"가벼운 계획, 주간 점검, 우선순위 압축 같은 실무 감각을 얻을 수 있음"},{"who":"창업자","why":"성장기 조직의 문화 관리와 불필요한 프로세스 제거 원칙이 유용함"}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 구간은 빠르게 성장하는 조직에서 문화와 실행 체계를 어떻게 유지할지에 대한 대화가 핵심이다. Airbnb에서의 경험을 바탕으로, 창업자가 문화에 집착하며 반복해서 상기시키는 것과, 문제를 숨기지 않고 솔직하게 말할 수 있는 분위기가 중요하다고 강조한다. 또한 Cloud Code 팀이 불필요해진 프로세스를 과감히 없애고, 계획도 길게 잡기보다 월 단위로 가볍게 보면서 매주 재점검하는 JIT(Just-in-time) 방식으로 운영한다는 점이 인상적이다.\n\n후반부에는 추천 도서·영화 이야기가 이어지지만, 전체적으로는 리더십의 태도와 일하는 방식에 대한 철학이 드러난다. 핵심은 '더 잘 굴리는 법'보다 '변화가 빠를수록 더 짧은 피드백 루프와 더 높은 솔직함이 필요하다'는 메시지다.","insights":["성장통은 문제라기보다 성장의 증거다.","문화는 선언보다 반복적 리마인드로 유지된다.","나쁜 소식은 숨길수록 해결이 늦어진다.","프로세스는 효율이 아니라 목적 기준으로 폐기해야 한다.","계획은 길게보다 짧고 자주 재점검하는 편이 낫다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c8:5-16","startSegmentIndex":5,"endSegmentIndex":16,"startTime":4824.56,"endTime":4948.4,"durationSeconds":123.8,"preview":"문화는 반복이다","mustSee":false},{"clipId":"Ybrl4FYM57c:c8:21-28","startSegmentIndex":21,"endSegmentIndex":28,"startTime":4983.32,"endTime":5066.6,"durationSeconds":83.3,"preview":"없앨 건 과감히 없애라","mustSee":true},{"clipId":"Ybrl4FYM57c:c8:31-43","startSegmentIndex":31,"endSegmentIndex":43,"startTime":5076.56,"endTime":5150.04,"durationSeconds":73.5,"preview":"JIT 계획의 원칙","mustSee":false},{"clipId":"Ybrl4FYM57c:c8:57-77","startSegmentIndex":57,"endSegmentIndex":77,"startTime":5237.68,"endTime":5397.48,"durationSeconds":159.8,"preview":"취향이 드러난 선택","mustSee":false}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T15:01:25.586Z","keyClipsTotalSec":1526},{"videoId":"Ybrl4FYM57c","chunkIndex":9,"totalChunks":10,"title":"How the most AI-pilled product team builds products | Fiona Fung (Claude Code and Cowork) — Part 10 of 10","thumbnail":"https://i.ytimg.com/vi/Ybrl4FYM57c/maxresdefault.jpg","duration":5925,"uploader":"Lenny's Podcast","youtubeUrl":"https://www.youtube.com/watch?v=Ybrl4FYM57c","keywords":["leadership","management","productivity","work-culture","kindness","personal-story","knitting","ai","startup","lifestyle"],"normalizedKeywords":["리더십·매니지먼트","커리어·성장","라이프스타일"],"targetAudience":[{"who":"리더","why":"우선순위, 1:1, 배려 같은 매니지먼트 원칙을 실전 경험으로 들을 수 있음"},{"who":"프로덕트 실무자","why":"단순하게 집중하는 태도와 사용자/동료 중심 사고를 배울 수 있음"},{"who":"지식노동자","why":"일과 삶에서 기억할 만한 짧은 원칙과 습관이 많아 보편적으로 유용함"}],"normalizedAudience":["지식노동자 일반"],"summary":"이 구간은 Fiona Fung이 자신에게 영향을 준 삶의 태도와 일하는 원칙을 가볍지만 진솔하게 풀어내는 마무리 대화다. 여행 중에 다시 깨달은 개인용 케어 제품의 중요성, 일에서의 ‘keep it simple’, 삶에서의 ‘be kind’, 그리고 코로나 시기에 경험한 1:1 일정 조정과 가족과의 FaceTime 같은 사례가 이어지며, 좋은 리더십은 거창한 말보다 작은 배려에서 드러난다는 점을 보여준다.\n\n후반부에서는 그녀의 취미인 뜨개질이 프로그래밍과 닮았다는 비유, 할머니에게 배운 기술이 지금도 정서적 연결고리로 남아 있다는 이야기, 그리고 언젠가 할머니 이름으로 실을 파는 공간을 열고 싶다는 꿈까지 나온다. 마지막에는 Claude 사용 사례 피드백과 주변 사람들에게 AI를 손잡고 소개해 달라는 요청으로, 기술 확산은 ‘설득’보다 ‘도움의 손길’이 중요하다는 메시지로 마무리된다.","insights":["좋은 리더십은 복잡한 이론보다 단순한 원칙에서 나온다.","사소한 배려 하나가 관계의 신뢰를 가장 크게 만든다.","1:1은 관리 일정이 아니라 상대의 중요한 시간을 존중하는 행위다.","반복되는 취미는 휴식이 아니라 정체성과 기억을 지키는 장치다.","새 기술의 확산은 설명보다 누군가를 직접 도와주는 순간에 일어난다."],"keyClips":[{"clipId":"Ybrl4FYM57c:c9:8-22","startSegmentIndex":8,"endSegmentIndex":22,"startTime":5432.44,"endTime":5543.08,"durationSeconds":110.6,"preview":"작은 습관의 영향","mustSee":false},{"clipId":"Ybrl4FYM57c:c9:28-45","startSegmentIndex":28,"endSegmentIndex":45,"startTime":5572.44,"endTime":5697.72,"durationSeconds":125.3,"preview":"단순함과 친절","mustSee":false},{"clipId":"Ybrl4FYM57c:c9:46-60","startSegmentIndex":46,"endSegmentIndex":60,"startTime":5697.72,"endTime":5804.56,"durationSeconds":106.8,"preview":"뜨개질과 정체성","mustSee":false},{"clipId":"Ybrl4FYM57c:c9:67-72","startSegmentIndex":67,"endSegmentIndex":72,"startTime":5839.68,"endTime":5892.52,"durationSeconds":52.8,"preview":"AI 확산의 방식","mustSee":true}],"curatedSegments":[{"segmentIndex":13,"text":"For anything that there is a fear, my advice is lean in and ask, [music]\"What can I do about it?","startTime":56.48,"endTime":60.92,"durationSeconds":4,"level":"B2","overallScore":7.8,"rationale":"두려움에 대한 실천적 조언임."},{"segmentIndex":87,"text":"And that's the shift that, you know, like we're seeing with uh Clockwork and Co-work is coding is no longer the bottleneck.","startTime":537.52,"endTime":544.64,"durationSeconds":7,"level":"B2","overallScore":7.4,"rationale":"핵심 변화와 그 의미를 한 문장에 담음."},{"segmentIndex":13,"text":"Um because if you're measuring like, you know, like tool user usage, then you're measuring the action, but is it really making whatever the end outcome of yours like important? Um and so I really uh try to zoom out and focus on what is the problem we're trying to solve?","startTime":2491.76,"endTime":2502.56,"durationSeconds":11,"level":"C1","overallScore":8,"rationale":"문제 정의로 관점을 넓히는 핵심 조언임."},{"segmentIndex":9,"text":"When I actually think as a leader, if you actually start as IC first without a like worry of supporting people cuz that's a very heavy responsibility that, you know, I think like managers, but like that but before you have to take on that full responsibility, give yourself that maker time to actually type deep into the code and learn the code base and I or the product, like whatever it is.","startTime":3051.56,"endTime":3062.6,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"리더십 조언과 학습 원칙이 뚜렷함."},{"segmentIndex":12,"text":"So even me doing PRs it's less about what it is I'm fixing, it's more about me using the product every day just to keep that touch cuz as amazing as metrics and everything are and I do look at those dashboards, if you as a leader if you're not, you know, like living and breathing your product every day you sometimes kind of like lose touch of uh touch and feel of the product.","startTime":3086.44,"endTime":3107.8,"durationSeconds":21,"level":"C1","overallScore":8,"rationale":"리더의 제품 몰입 필요성을 잘 짚음."},{"segmentIndex":64,"text":"So, the idea here is like almost pair programming, but not. It's like parallel play when kids are growing up.","startTime":3457.56,"endTime":3466.76,"durationSeconds":9,"level":"B2","overallScore":7.8,"rationale":"비유로 새 개념을 잘 설명함."},{"segmentIndex":35,"text":"Um one time I had like a MacBook Air and I wanted to sell my old and you know, I haven't sold anything on Marketplace let me and I could not believe it the minute I put it up for sale a seller or buyer tried to scam me and it was an interesting like new scam vector I didn't detect and so but that goes to again like people will use uh your products in ways that you may not expect and so especially as leaders or even like anyone on the team, we all have different like life like actually it's funny when it when I was a you know, supporting the VR and AR teams, somehow how I used VR, the setup, I would always be able to find these really weird floor height issues.","startTime":3882.76,"endTime":3922.12,"durationSeconds":39,"level":"C1","overallScore":7.8,"rationale":"생생한 사례와 학습 포인트가 큼."},{"segmentIndex":71,"text":"And so, the culture of the team is important to me because we are growing and are we are growing and since the culture shifts like making sure that maintaining the things are important that we are we still really like it's really important for me to have like diverse perspectives so then we can have you know like good healthy open honest debates on in the open and we kind of like welcome those and kind of what I call that one team mentality that when you get close to the finish line look behind you and see is there some of our team to help cuz we kind of finish as a team.","startTime":4712.52,"endTime":4742.28,"durationSeconds":30,"level":"C1","overallScore":7.8,"rationale":"성장 속 문화 유지 원칙을 구체적으로 제시함."},{"segmentIndex":72,"text":"That's probably the thing that keeps me up at night and it's like you know there's so many other hard problems right but I think maybe a lot of the other ones are product or engineering challenges that yes we have you know like dashboards or theories or hypotheses like but the culture is like a human aspect that is um Like I think that's the one that I always want to make sure that we're as we grow we're still kind of like maintain that culture cuz it is kind of like the fiber of the team and it like when it starts drifting it it's it I'm always worried of you know like if it drifts are we catching it and having conversations as a team together to make sure we're kind of all wanting the culture to grow in the right direction.","startTime":4742.28,"endTime":4789.12,"durationSeconds":47,"level":"C1","overallScore":7.6,"rationale":"성장 속 문화 드리프트를 핵심 문제로 봄."},{"segmentIndex":5,"text":">> things one is just the what worked well is the founders being obsessed with it like every all hands every big meeting is just like reminding of like the culture and the value of the culture and what the values are just the founders top-down being obsessed with it was a really big part of it.","startTime":4824.56,"endTime":4835.4,"durationSeconds":11,"level":"C1","overallScore":7.8,"rationale":"문화 유지의 핵심 원칙을 구체화."},{"segmentIndex":8,"text":"Because we're just going so fast and it's so hard to mean deal with all this change and culture and all these new people and her advice was this is actually the what the problem you want to have because this means you're growing and doing well and this is normal versus you can nothing will change if you're doing badly like that's the that's so much worse situation when you're not growing and you're not hiring like crazy.","startTime":4858.56,"endTime":4881.92,"durationSeconds":23,"level":"C1","overallScore":7.6,"rationale":"성장과 어려움을 재해석하는 조언."},{"segmentIndex":5,"text":">> The people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.","startTime":18.2,"endTime":22.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"성과 요인을 일반화해 말함."},{"segmentIndex":11,"text":">> Something you think about is this gap forming [music] between people that are leaning into AI, killing it, and then people that are not, super frustrated, fighting, resisting.","startTime":44.12,"endTime":52.24,"durationSeconds":8,"level":"B2","overallScore":6.8,"rationale":"대조 구도로 상황 인식을 보여줌."},{"segmentIndex":40,"text":">> Oh, I love this kind of look back in time. Yeah, like IBM, working on DB2, the operating system services team. Like I remembered I wanted to first and foremost create a delightful experience not only for myself, but for my teammates.","startTime":243.44,"endTime":250.36,"durationSeconds":7,"level":"B2","overallScore":6.8,"rationale":"경험담과 가치 기준이 드러남."},{"segmentIndex":67,"text":"But back then I was so lucky because I was on VS. We ourselves gave each other so much rapid feedback cuz we were all heavy VS users on the team.","startTime":402.15999999999997,"endTime":409.84000000000003,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 내부 피드백 경험이 잘 드러남."},{"segmentIndex":84,"text":"And I think that's the interesting thing and I kind of mentioned this in my talk. It's before when you like engineering time was like really precious resource.","startTime":517.28,"endTime":526.4,"durationSeconds":9,"level":"B2","overallScore":6.6,"rationale":"자원 인식의 변화를 일반화함."},{"segmentIndex":89,"text":"So but now it's all about like where has that shift happened? Like now not only engineers but we also have designers, PMs, everybody on the Clockwork team checks in code.","startTime":548.72,"endTime":556.92,"durationSeconds":8,"level":"B2","overallScore":6.6,"rationale":"팀 구성 변화와 협업 확장을 설명함."},{"segmentIndex":91,"text":"How do we think about verification? Like that's kind of this other shift that I'm seeing.","startTime":563.16,"endTime":567.52,"durationSeconds":4,"level":"B2","overallScore":6.8,"rationale":"검증이라는 새 과제를 문제화함."},{"segmentIndex":13,"text":"Like it's okay to make mistakes, just make new ones so that we're always learning cuz if you aim to make zero mistakes, like that probably means you're not, you know, moving fast enough or being a little bit too cautious.","startTime":691.2,"endTime":702.2,"durationSeconds":11,"level":"B2","overallScore":6.8,"rationale":"실수와 속도에 대한 분명한 교훈이 있음."},{"segmentIndex":58,"text":"So, the two profiles that you now look for when you're hiring are creative builders with product sense and deep systems experts for the hard parts.","startTime":1028.959,"endTime":1038.199,"durationSeconds":9,"level":"C1","overallScore":6.6,"rationale":"채용 기준을 선명하게 요약한다."}],"generatedAt":"2026-06-22T15:01:46.986Z","keyClipsTotalSec":1526}]}