#transcript — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #transcript, aggregated by home.social.
-
In this #InfoQ #podcast, Adam Bien highlights the importance of consistently using standards - whether in Java or established patterns.
He explains how this approach helped future-proof the systems he built, making them adaptable for both the cloud era & the AI-native era.
🎧 Listen now: https://bit.ly/49w4QP5
📄 #transcript included
-
#ClaudeCode is built to maximize AI development velocity.
People often look for hidden complexity or secret architecture in AI tools. The reality is far more disciplined:
• Async generators
• Well-typed interfaces
• Simple orchestration patternsThe real innovation was deliberately choosing simplicity to move faster.
In this #InfoQ video, Adam Wolff explores the architectural decisions that prioritize speed over complexity - and how this velocity-first approach leads to process–product convergence, where internal workflows evolve into user-facing capabilities.
🎬 Watch now: https://bit.ly/3RwBgTm
📄 #transcript included
-
In tech, we know how to scale systems. But scaling humans? Well … that’s another story.
Even with the right tools and processes, technical teams often struggle to scale behaviorally & culturally.
In this #InfoQ video, Charlotte de Jong Schouwenburg explores why behavioral and cultural scaling is harder than technical scaling - and what leaders and teams can do about it.
🎬 Watch now: https://bit.ly/4uw8ctk
📄 #transcript included
-
In this #InfoQ #podcast, Andy Damevin (long-time Quarkus contributor) explores #Roq - a static site generator built on top of #Quarkus.
He covers:
• The motivation behind the project
• Why Java & Quarkus were chosen
• Migration to Roq
• Its future direction🎧 Listen now: https://bit.ly/4n6MiKQ
📄 #transcript included -
#EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.
In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.
🎬 Watch now: https://bit.ly/41NZqLe
📄 #transcript included
-
“𝑊𝑒 𝑐𝑜𝑢𝑙𝑑 ℎ𝑎𝑣𝑒 𝑐𝑎𝑙𝑙𝑒𝑑 𝑡ℎ𝑖𝑠 𝑡𝑎𝑙𝑘 ‘𝐻𝑜𝑤 𝑤𝑒 𝑑𝑜𝑢𝑏𝑙𝑒𝑑 #𝐸𝑛𝑔𝑖𝑛𝑒𝑒𝑟𝑖𝑛𝑔𝑃𝑟𝑜𝑑𝑢𝑐𝑡𝑖𝑣𝑖𝑡𝑦 𝑎𝑡 𝑒𝐵𝑎𝑦’ - 𝑤ℎ𝑖𝑐ℎ 𝑤𝑒 𝑑𝑖𝑑 - 𝑏𝑢𝑡 𝑤𝑒 𝑠𝑡𝑖𝑙𝑙 𝑑𝑖𝑑𝑛’𝑡 𝑠𝑎𝑣𝑒 𝑡ℎ𝑒 𝑐𝑜𝑚𝑝𝑎𝑛𝑦. 𝑇ℎ𝑒𝑛 𝐼'𝑚 𝑔𝑜𝑖𝑛𝑔 𝑡𝑜 𝑡𝑒𝑙𝑙 𝑦𝑜𝑢 ℎ𝑜𝑤 𝐼 𝑔𝑜𝑡 𝑓𝑖𝑟𝑒𝑑 𝑓𝑜𝑟 𝑖𝑡”.
In this #InfoQ video, Randy Shoup breaks down the “Middle-Out” strategy behind the transformation and the brutal reality of the Innovator’s Dilemma:
🏆 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐞𝐱𝐜𝐞𝐥𝐥𝐞𝐧𝐜𝐞 𝐚𝐥𝐨𝐧𝐞 𝐜𝐚𝐧’𝐭 𝐬𝐚𝐯𝐞 𝐚 𝐜𝐨𝐦𝐩𝐚𝐧𝐲 𝐢𝐟 𝐭𝐡𝐞 𝐜𝐮𝐥𝐭𝐮𝐫𝐞 & 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐰𝐨𝐧’𝐭 𝐜𝐡𝐚𝐧𝐠𝐞!
🎬 Watch now: https://bit.ly/481Up5i
📄 #transcript included
#SoftwareEngineering #DevOps #EngineeringLeadership #CaseStudy #DORA
-
In this #InfoQ #podcast, Sam Bhagwat, co-founder & CEO of Mastra, shares insights on building and sustaining #opensource communities, the emerging discipline of #AI engineering and evals, and why cross-functional Tiger Teams are key to shipping agentic applications.
🎧 Listen now: https://bit.ly/4tQpH7w
📄 #transcript included
-
Как я выбираю моменты для Shorts: почему LLM + транскрипт почти всегда дают мусор
Это третья статья про мой "аниме завод" — систему, которая автоматически превращает длинные эпизоды в Shorts. Если хотите полный контекст, вот предыдущие части:
https://habr.com/ru/articles/1021552/
#llm #shorts #python #cv #computer_vision #signal_processing #multimodal #transcript #youtube_shorts #ai
-
#AICodingAgents are evolving fast.
In this #InfoQ video, Sepehr Khosravi breaks down today’s leading tools (Cursor, Claude Code, and beyond), where each excels, and how to get production-ready results.
Learn:
🔹 What each top AI coding agent is best (and worst) at
🔹 Best strategies that improve code quality
🔹 How to evaluate and choose copilots that genuinely boost team velocity🎬 Watch now: https://bit.ly/4sslG8m
📄 #transcript included
𝐖𝐡𝐨 𝐬𝐡𝐨𝐮𝐥𝐝 𝐰𝐚𝐭𝐜𝐡? Software Engineers, Product Managers, AI enthusiasts, and technical leaders looking to maximize engineering productivity with GenAI.
-
Stop thinking of your career as a ladder!
A #TechCareer is not short, straight, or evenly spaced - it is a long, winding, and often challenging journey.
In this #InfoQ video, Sophie Weston shares how she grew from Junior Developer → #PrincipalEngineer, covering the skills, strategies, and support that shaped her path.
🎬 Watch now: https://bit.ly/4toP00f
📄 #transcript included
-
Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.
#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.
3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.
🚫 No app store update required.
🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N
📄 #transcript included
#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering
-
Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.
#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.
3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.
🚫 No app store update required.
🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N
📄 #transcript included
#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering
-
Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.
#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.
3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.
🚫 No app store update required.
🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N
📄 #transcript included
#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering
-
Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.
#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.
3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.
🚫 No app store update required.
🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N
📄 #transcript included
#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering
-
Shipping mobile updates is a bottleneck: app store reviews, slow user updates, multiple versions in the wild.
#Nubank flipped the model with Catalyst - a scripted Server-Driven UI (#SDUI) framework that ships more than just layouts.
3,000+ engineers can now deploy UI changes and complex business logic to 115M+ users in under 20 minutes.
🚫 No app store update required.
🎬 Watch the architecture deep dive ⇨ https://bit.ly/4lIUY9N
📄 #transcript included
#MobileDevelopment #SoftwareArchitecture #UserInterface #ServerSideRendering
-
@Author-ized L.J. That's the problem: Whatever I do, I'll lose either way.
On the one hand, I feel a great pressure to describe and explain everything in advance. That way, nobody would ever have to ask me to describe a detail or explain something. And nobody, not even the most die-hard Mastodon alt-text activists, could say that I'm careless and that I only do the very bare minimum or not even that. There are people out there who are eager to block everyone who doesn't describe their images enough or lecture them or attack them for being lazy.
The last time I've described an image for Hubzilla, I refused to write detailed descriptions for the images within that image. That would have escalated and cost me weeks to describe them all because I'd also have had to describe dozens of images within these images and even more images within these images. Mind you, someone who travels to the place I've described couldn't actually see what I'd have described because the images in my image themselves have a limited resolution. But I genuinely felt bad for not describing these images.
Besides, if I only described my original images once, namely in the alt-text, and then briefly and concisely, and if someone came and asked me to describe certain elements at greater detail, I couldn't always do that. Sometimes I couldn't go back to the place shown in the image and take a closer look and write a more detailed description because that place simply doesn't exist anymore, or it has been modified, and it doesn't look like the image anymore. The details that I'd have to take a closer look at are gone.
On the other hand, my experience is also that posting more than 500 characters at once reduces my reach on Mastodon tremendously. I think I must have over 700 or 800 followers, but my reach on Mastodon is similar to that of someone with not even a dozen followers. And I don't think that's because what I post is so uninteresting or because of my rather controversial thoughts about the Fediverse, accessibility in the Fediverse, image descriptions etc.
Basically, I can't possibly post images without risking being sanctioned by anyone.
I've briefly considered putting my long descriptions into separate HTML documents and linking to them. In theory, that would reduce the length of my image posts greatly. However, this is entirely untested. I don't know if it'd work at all, i.e. open the HTML document in someone's browser rather than downloading it to their device as a file. I don't know either if a plain HTML document with no style sheet would be accessible to screen reader users.
What I do know, though, is that Mastodon hates external links with a flaming passion. That's also because the vast majority of Mastodon users is always on phones, using dedicated Mastodon apps. They hate their browser popping open when they tap a link all the same. Also, they tend to distrust external links because the linked documents or pages may not be sufficiently accessible.
Everything would be a whole lot easier if there were Fediverse-wide standards for image descriptions that take the requirements of blind or visually-impaired people into consideration as well as Mastodon's unique culture. If these standards were known to everyone both on Mastodon and in the non-Mastodon Fediverse. If everyone from blind or visually-impaired users to neurodivergent users to fully sighted alt-text activists agreed upon these standards all the same. And if these standards covered extreme edge-cases like mine as well. If there was a generally agreed-upon consensus on a whole lot of questions like:- Is it okay to have to ask for detailed descriptions of certain details in an image that don't matter within the context of the post?
Or do they have to be described right away if there's a chance that someone might be curious about them? What if nothing specific in the image matters more within the context than everything else? - Is it okay to have to ask for explanations if you don't understand the topic of an image?
Or do images about very obscure niche topics have to come with enough explanations for everyone to understand them right away (not counting technical or jargon terms which always have to be either avoided or explained)? - So there's the rule that all text within an image must be transcribed verbatim. How far does this rule go?
Let's suppose I have a few dozen individual bits of text within an image. Most or all of them are so small that they're unreadable. Some are so tiny that they're actually invisible at the image's resolution. Still, technically speaking, they're there. And: I can read them. Instead of reading them in the image, I can read them at the source. So I can transcribe them all.
What is the rule then?
Do I have to transcribe them although they're unreadable because the rule says all text has to be transcribed?
Do I have to transcribe them although they're unreadable because not doing so and writing that they're unreadable with no transcript is or may be considered lazy?
Do I have to transcribe them because they're unreadable, and even fully sighted people need a transcript to know what's written there?
Mustn't I transcribe them because they don't show themselves as text in the image at the image's resolution (if they actually don't)?
Mustn't I transcribe them because I must only describe what's visible in the image at the image's resolution to the naked eye?
Do I have to transcribe them in my special edge-case in spite of the two above lines because this might be my last and only chance to transcribe them, for they may be gone tomorrow, and I would no longer be able to transcribe them if someone asked for a transcript? Or must I remember to keep personal transcripts of all the texts I come across in my images, just in case someone asks for a transcript of a bit of text that no longer exists? - Must all text transcripts always be in the alt-text as opposed to an extra long image description in the post? Even if I have 20+ individual text transcripts to squeeze into Mastodon's limit of 1,500 characters of Misskey's limit of 512 characters?
Or is it okay to- transcribe them in a separate long description in the post text
- not put these transcripts into the alt-text
- mention in the alt-text that there is a long image description in the post, that all the texts in the image are transcribed there, and how exactly to find that long image description?
- If any of the above requires a separate long image description because the image description won't fit within the alt-text character limits, is it preferred for the long description to be in a linked document that will open in the browser (given one has the means to write and host such a document, and users on Hubzilla, (streams) and Forte do have these means)?
Or must the long description be where the image is at all costs? Must it be in the post itself for the convenience of app users even if it inflates the post to a hyper-massive length to the inconvenience of Mastodon users?
Worse yet: I've recently found out that none of the things above must be discussed on Mastodon. Ever. You must not discuss that stuff. You must do it. But you must do it right off the bat. For whichever individual definition of "right".
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #A11y #Accessibility - Is it okay to have to ask for detailed descriptions of certain details in an image that don't matter within the context of the post?
-
Transcript: Sen. Ted Cruz on "Face the Nation with Margaret Brennan," March 1, 2026
https://misryoum.com/us/politics/transcript-sen-ted-cruz-on-face-the-nation/
The following is the transcript of the interview with Sen. Ted Cruz, Republican of Texas, that aired on "Face the Nation with Margaret Brennan" on March 1, 2026.MARGARET BRENNAN: We go now to Texas Republican Senator Ted Cruz, who...
#Transcript #Sen #Ted #Cruz #Face #the #Nation #with #Margaret #Brennan #March #2026 #US_News_Hub #misryoum_com
-
Managing 10 engineers is a job. Leading 100+ is a completely different game.
This is the point where most engineering careers stall. 🛑
In this new #InfoQ video, Thiago Ghisi shares hard-earned, tactical lessons from 8 years across American Express, Apple, and Nubank.
If you're a Staff+ engineer, Engineering Manager, or aspiring Director, this breaks down how to evolve from being the person who solves problems to the leader who drives organizations - without sacrificing resilience.
🎬 Watch now | 📄 #transcript included ⇨ https://bit.ly/3ZXRLsw
-
#House #Judiciary Committee on 12/31/25 released full #deposition #transcript of former #SpecialCounsel #JackSmith, offering most detailed public account yet of Smith’s rationale 4 prosecuting #DonaldTrump #Jan6 #insurrection rebutting #Republican #GOP #maga claims that investigations were politically motivated. #law #legal #government #democracy #legalresearch #Congress #constitution #violence #indictments #grandjury https://judiciary.house.gov/sites/evo-subsites/republicans-judiciary.house.gov/files/2025-12/Smith-Depo-Transcript_Redacted-w-Errata.pdf See Also 8hrs video testimony https://www.youtube.com/watch?v=lR-bhPzQYUE
-
Transcript available for 1.7: Bioluminescence: The Soft Glow of the Deep Sea with Dr. Steve Haddock on our #Patreon - it's a free-access post. https://patreon.com/solarpunkpresents
#transcript #podcastTranscript #EpisodeTranscript #SeasonOne #SolarpunkPresentsPodcast #solarpunk #Interview #Bioluminescence #Oceanography #Oceans #BioMimicry #lunarpunk #aesthetic #DeepSea #Ocean
-
Transcript available for 1.6:Talking About 'Bioluminescent: A Lunarpunk Anthology' With Justine Norton-Kertson on our #Patreon - it's a free-access post. https://patreon.com/solarpunkpresents
#transcript #podcastTranscript #EpisodeTranscript #SeasonOne #SolarpunkPresentsPodcast #solarpunk #bioluminescence #lunarpunk #JustineNortonKertson #SolarpunkMagazine #Interview #SolarpunkFiction
-
Transcript available for 1.5: Defending Democracy Via Urban Planning with Dr Jayde Lin Roberts on our #Patreon - it's a free-access post. https://patreon.com/solarpunkpresents
#transcript #podcastTranscript #EpisodeTranscript #SeasonOne #SolarpunkPresentsPodcast #solarpunk #Interview #UrbanPlanning #Democracy #Infrastructure
-
Transcript available for 1.4: Coping with Climate Grief with Gabrielle Chapman on our #Patreon - it's a free-access post. https://patreon.com/solarpunkpresents
#transcript #podcastTranscript #EpisodeTranscript #SeasonOne #SolarpunkPresentsPodcast #solarpunk #Interview #ClimateGrief #ClimateAnxiety #ClimateChaplain #Faith #Spirituality
-
Transcript for S1E4: Coping With Climate Grief, With Chaplain Gabrielle Gelderman now available for public download: https://www.patreon.com/c/solarpunkpresents
Let me know if there are any glaring errors.
#SolarpunkPresentsPodcast #solarpunk #podcast #transcript #SeasonOne #PodcastTranscript #EpisodeFour
-
Hey friends, the transcript for S1.3: Climate Change and the Marshall Islands, With Dr Helene Jacot Des Combes is posted for free on our Patreon: https://www.patreon.com/posts/transcript-for-3-132375124
#Transcript #PodcastTranscript #Podcast #Solarpunk #MarshallIslands #ClimateChange #SeaLevelRise
-
The transcript for episode 1.2 is now available here: https://www.patreon.com/posts/124123344
I've added it in to YouTube and the podcast description itself so it is accessible everywhere :)
#SolarpunkPresentsPodcast #PodcastTranscript #SeasonOne #Transcript
-
Cannot remember if I've posted about this already, so apologies if this is a duplicate, but the transcript for episode 7.3 is now available here: https://www.patreon.com/posts/125524354?collection=1380839
I've added it in to YouTube and the podcast description itself so it is accessible everywhere :)
#SolarpunkPResentsPodcast #PodcastTranscript #SeasonSeven #Transcript
-
Einzelne Mitarbeitende des #BBSR haben gesammelte Werke in einem #OpenAccess #Bauwende-Buch im #transcript-Verlag veröffentlicht. Es tauchen viele interessante Schlagworte auf: #Lebenszyklus, #CO2-Budget/-Zielpfad, #Suffizienz, #Quartiersansatz....
#Bauwende #Effiienzwende #lessismore #verbietetdasbauen #Sanierung #Gebäudebestand #Ressourcenschutz
-
CW: #Digital #Coup = #TechBros + #Oligarchy (#Broligarchy)
#Digital #Coup = #TechBros + #Oligarchy (#Broligarchy)
"This Is What a Digital Coup Looks Like" - #CaroleCadwalladr #Quote
https://inv.nadeko.net/watch?v=TZOoT8AbkNE
OR with #transcript
https://www.ted.com/talks/carole_cadwalladr_this_is_what_a_digital_coup_looks_like/transcript
#Cadwalladr #DigitalCoup
#Privacy #Data #DataHarvesting
#Broligarchy = #TechBros + #Oligarchy -
Hey friends, the transcript for 7.3 is available now at https://www.patreon.com/posts/125524354 - it's a free post, so anyone should be able to access it; let me know if you're having difficulties.
We'll be attaching it to the blog post, YouTube vid, and Acast in the next little while. Happy Sunday!
#Episode #transcript #SolarpunkPresentsPodcast #PodcastTranscript #Season7 #Episode3
-
In this #InfoQ talk, Shweta Saraf introduces a powerful framework for developing #StrategicThinking, designed for engineers at any career stage - with an emphasis on #StaffPlus roles.
Whether you're an experienced Staff+ engineer or aiming to reach that level, Shweta’s insights provide the tools and perspectives to elevate your career and navigate new challenges in your engineering career.
Watch the video now: https://bit.ly/3YMS7Tc
#transcript included
-
The transition to #StaffPlusEngineer isn't just about technical excellence - it is about how you influence, lead & drive outcomes across your organization.
In this #InfoQ video, Thiago Ghisi, explores:
➡️ What defines the Staff-Plus level, common expectations across companies, and the key gaps that often cause Senior Engineers to get stuck
➡️ Strategies for scaling personal impact through mentorship, sponsorship, and strategic involvement in projects
➡️ Concrete examples of "Staff Projects" that define success at this level👀 Watch now: https://bit.ly/3LqRLdz
#transcript included
-
I'd like to kindly ask #podcasts to:
- Provide a #transcript for every episode
- Add human-readable #TimeCodes to that transcript, in key places
- Highlight #sections / #topics / #questions, in that transcript, by turning them into headingsThat's it. That's the post.
-
I'd like to kindly ask #podcasts to:
- Provide a #transcript for every episode
- Add human-readable #TimeCodes to that transcript, in key places
- Highlight #sections / #topics / #questions, in that transcript, by turning them into headingsThat's it. That's the post.
-
I'd like to kindly ask #podcasts to:
- Provide a #transcript for every episode
- Add human-readable #TimeCodes to that transcript, in key places
- Highlight #sections / #topics / #questions, in that transcript, by turning them into headingsThat's it. That's the post.
-
Once you get that #StaffPlus role:
➡️ You are expected to be more autonomous and might be working across multiple teams.
➡️ You might not be “on the ground” working day-to-day within a team.
➡️ Coding is just one of the ways you deliver value.Your role now is to gather context & evaluate opportunities to help shape what you and other teams should focus on.
Watch the #InfoQ video to gain more insights: https://bit.ly/4aNLHY9
#transcript included
-
Watch this #Infoq video on #PsychologicalSafety in #SoftwareTeams!
Discover why it matters to software teams and how #StaffPlus engineers can foster environments high in psychological safety: https://bit.ly/3NaT7dN
“Psychological safety is foundational to high-performing teams. If people won't, or can't speak up, then we risk not hearing valuable information until it's too late. One of the best ways to increase interpersonal risk-taking in our teams is for us to model these types of behaviors regularly and consistently. My question to you is, when would you get started?” Jitesh Gosai - Principal Tester at BBC
#transcript included
-
DSoes anyone have a #transcript of #TraitorTot #Boebert 's nomination rant from vote # 5?
-
Ethics in the age of autonomous vehicles - Earlier this month, TechCrunch held its annual Mobility Sessions event, where leading mobility-focus... more: http://feedproxy.google.com/~r/Techcrunch/~3/ZJzqpjlb7fE/ #tcsessions:mobility2019 #artificialintelligence #autonomousvehicles #self-drivingcars #transportation #micromobility #olivercameron #automotive #transcript #personnel #rideshare #startups #mobility #ridehail #scooters #policy #talent #ethics #voyage #uber
-
‘This is Your Life in Silicon Valley’: Philz Coffee CEO Jacob Jaber on tech culture and Blue Bottle - Welcome to this week’s transcribed edition of This is Your Life in Silicon Valley. We’re running an ... more: http://feedproxy.google.com/~r/Techcrunch/~3/1AyTZRH5YPA/ #thisisyourlifeinsiliconvalley #sanfranciscopolitics #podcasttranscript #localgovernment #sunilrajaraman #philzcoffee #government #bluebottle #jacobjaber #transcript #starbucks #startups #policy #coffee #tc
-
An Equity deep dive on Patreon - The popular TechCrunch podcast Equity this week launched a new series called Equity Dive, wherein a ... more: http://feedproxy.google.com/~r/Techcrunch/~3/RUUkgMS1r8Q/ #podcasttranscript #venturecapital #entertainment #equitypodcast #transcripts #transcript #podcasts #startups #creators #patreon #content #media #ec-1 #tc