Robin Heinze and Tyler Williams of Infinite Red unravel Fabric, React Native’s modern rendering system. No sewing required! They explain how Fabric speeds up mobile apps and unlocks concurrent React features for smoother software engineering.
Infinite Red is a premier mobile app consultancy, especially focused on Expo and React Native, located fully remote in the US. We’re a team of 30 with highly experienced mobile app developers and have been doing this for over a decade. We are also one of the first development teams to adopt agentic coding in a way that keeps high quality standards and aren’t afraid to do things the old school way if we need to. If you’re looking for mobile app or React Native or Expo expertise for your next project, hit us up at infinite.red/radio.
Description: TypeScript technical fellow Anders Hejlsberg introduces TypeScript 7, the native code (Go) port of the compiler and tooling that runs roughly 10x faster than TypeScript 6.
Watch a live compile of the 2.3M-line VS Code codebase drop from 50s to under 5s, see how shared-memory concurrency uses every core, and check out the new LSP-based language server with near-instant references, squiggles, and startup — all with 99.99% compatibility with TypeScript 6.
01:26 Why the JavaScript compiler hit its limits 02:49 Where the 10x comes from: native code + concurrency 04:29 Live demo: compiling VS Code in seconds 07:01 The new LSP language server & migration guidance
Welcome back to another episode of The Download! This week, we cover TypeScript 7 shipping a new native Go compiler that delivers massive 8x to 12x speedups for large codebases. We also explore VS Code 1.129's dedicated agent host runtime, Kimi K3's 2.8 trillion parameter model, and the open sourcing of Microsoft's classic 1996 Comic Chat IRC client. Plus, inspect what Cargo actually downloads on crates.io, bring classic AIM back with Open OSCAR Server, and get your tickets for GitHub Universe 2026.
#VSCode #TypeScript #Microsoft
— CHAPTERS —
00:00 Welcome to The Download 00:37 TypeScript 7 gets a native compiler 01:22 Kimi K3 arrives 01:56 VS Code adds an agent host and bang commands 02:33 Microsoft Comic Chat goes open source 03:19 crates.io lets you inspect published code 03:55 Open OSCAR Server brings AIM and ICQ back 04:23 World Cup 2026 Data Portraits 05:04 GitHub Universe reminder 05:23 Outro
About GitHub It’s where over 180 million developers create, share, and ship the best code possible. It’s a place for anyone, from anywhere, to build anything—it’s where the world builds software. https://github.com
Which is more important, the model or the “harness” around an LLM? What are ways to assemble an efficient agentic developer workflow? This week on the show, Ayan Pahwa joins us to discuss harnessing, web scraping, and self-hosting Python applications.
Ayan is a developer advocate at Zyte and an experienced project builder. We discuss a recent article he wrote about creating an extension for the web scraping tool Scrapy. He also digs into his self-hosting setup for Python applications and tools.
Our discussion extends to the complexities of developing effective harnesses. Ayan shares his setup and how he navigated shifting from prompt engineering to context and loop engineering.
In this video course, you’ll learn all about web scraping in Python. You’ll see how to parse data from websites and interact with HTML forms using tools such as Beautiful Soup and MechanicalSoup.
Topics:
00:00:00 – Introduction
00:02:01 – Scrapy and building an extension
00:08:46 – Zyte and the web scraping API
00:11:19 – Sponsor: HydraDB
00:12:22 – noalgotube project
00:15:49 – Homelab & self hosting projects
00:22:19 – What goes into a harness?
00:32:33 – Where did you start exploring LLM tools?
00:36:13 – Local models & edge computing
00:39:31 – ExtractPod and discussing Apple’s AI
00:43:35 – Video Course Spotlight
00:44:54 – Managing token use and tools
00:52:37 – What are you excited about in the world of Python?
00:55:10 – What do you want to learn next?
00:56:38 – What is the best way to follow your work online?
Alf Dobbert-Baums: The Too-Technical PO and the One Who Was Willing to Experiment
In this episode, we refer to Shift: From Product to People and the value of keeping the PO–developer conversation at the goal level.
The Great Product Owner: The PO Who Was Willing to Drop the Spec and Trust the Developers
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
"Let's ditch the technical part, and let's see what happens." - Alf Dobbert-Baums
The Great PO, in Alf's experience, is willing to experiment with letting go. She stopped writing detailed technical specifications and started writing plain user stories. Then — and this is the harder move — she stopped throwing them over the fence and walked into the developers' space to have the conversation. Alf had coached her toward it, and he watched the trust compound. Because she trusted the developers on the how, she had less work to do (the developers were closer to the system anyway) and the developers had room to make real decisions. The conversation stayed where it belonged: on the goal. Alf names the pattern this great PO embodied — open to experiments, willing to say "let's see what happens," and quietly resisting the seductive pull of getting technical because it feels safer. The Scrum Master's job is partly to make that letting-go feel safe enough to try.
Self-reflection Question: Where is your PO still writing the "how" — and what would it take for them to trust the developers enough to write only the "why" and the "what"?
The Bad Product Owner: The PO Who Thinks They Know More Than the Developers
Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
"He said: 'developers can retrieve the information from the archive database.' The developer said: 'the information is not in the archive database.'" - Alf Dobbert-Baums
The anti-pattern is the PO who is too technical — the one who writes specs full of implementation detail and treats the developers as executors. Alf calls him John. John wrote a user story that told the developers exactly where to fetch the data from: the archive database. Then he tried to hand the story to Alf to present, the way a memo gets handed across a desk. Alf refused. He insisted John present it to the developers himself. John did. The first developer to speak said the information wasn't in the archive database. Alf hopes that moment humbled John a little. The point isn't whether John was right about the database — the point is the dynamic. When the PO writes the technical answer into the story, the developers stop being collaborators and become receivers. The translation work that creates real value — between user goal and technical option — never happens. The PO ends up with more work, less ownership from the team, and worse outcomes.
In this segment, we refer to Shift: From Product to People and the idea that great POs facilitate the conversation between user goal and team, rather than dictating it.
Self-reflection Question: When was the last time your PO wrote a technical detail into a story and the developers had to walk it back — and what would change if the PO trusted them to design the "how"?
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
Alf lives in Berlin. He studied Theater/Religion at the Freie University Berlin. He is a Systemic Organizational Consultant, a Scrum Master and Agile Coach. He has also been a freelancer for Usability and Requirements Engineering for car manufacturers. At "Verti" he led the agile transformation.
Log in
