Can tooling make event sourcing implementations easier? Carl and Richard talk to Einar Ingebrigsten about his work on cratis.io - a set of open-source tools for implementing event sourcing in your application. Einar discusses the foundational elements of event sourcing and the common implementation patterns he developed at Cratis. With extensive support for .NET, Cratis provides tooling for data storage, event response, replay management, and much more. Also in development is Cratis Studio for collaborating visually on an event model - and generating the code in the process.



Download audio: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/72468473/dotnetrocks_2006_event_sourcing_using_cratis.mp3

Jure Leskovec, Professor of Computer Science at Stanford University and Chief Scientist at Kumo.ai, speaks with host Sriram Panyam about relational and graph language models and their transformative impact on enterprise decision-making and predictive modeling.

Jure begins by establishing the critical importance of predictive modeling across industries - from fraud detection in financial institutions to customer churn prediction, lifetime value estimation, product recommendations, and healthcare risk assessment. He notes that while AI has made remarkable advances in natural language understanding and computer vision, predictive modeling over enterprise operational data stored in relational databases has been largely left behind, still relying on 30-year-old machine learning approaches that are expensive, time-consuming, and require manual feature engineering.

His proposed solution to the fundamental problem with current approaches is relational deep learning and relational transformers. The discussion explores how this approach differs from traditional graph neural networks (GNNs), which Jure pioneered and deployed successfully at Pinterest. Jure concludes with practical guidance for software engineers and data scientists interested in exploring this technology.

Download audio: https://traffic.libsyn.com/secure/seradio/724-jure-leskovec-relational-graph-models.mp3?dest-id=23379

If you think code is safe from automation, think again. This week's discussion tackles why the rise of vibe coding and AI-powered tools could upend long-held beliefs about software development, with even seasoned pros rethinking their roles. Also, a new C++ documentary is worth watching!

Windows

• After a weekend of Build session viewing, two big takeaways!
• Vibe coding native Windows apps and a new reactive dev model for WinUI will help to make modern app dev easier for everyone
• A new theory emerges: The real reason Microsoft is fixing Windows 11 is that it needs this foundation for a future of hybrid AI agents. And hybrid means more than just local + cloud.
• Patch Tuesday is here! As promised, Microsoft fixed a record number of security issues thanks to AI
• 24H2/25H2: Shared audio, more NPU in Task Manager, multi-app camera support, user folder name choice in OOBE, more
• 26H1: Xbox Mode, Drop tray, etc.
• Windows Insider Program: New 26H1 Beta channel added for some reason
• Dell now sells a Windows Hello ESS-compatible wired mouse

AI

• WWDC 2026: Apple announced vibe-coding advances for normal users (Safari extensions) and developers (Xcode). Paul used Xcode and Claude Code to create a full-featured Markdown editor app in about 12-15 minutes.
• Google drops the price of AI Plus plan to $4.99 per month, raises storage to 400 GB and announces new NotebookLM capabilities
• Proton Drive is coming to Linux, has a new SDK, and now has a new CLI too. We're going to need a CLI section in the show notes.

XBOX and gaming

• Microsoft Games Showcase: It needed to be a big day for Xbox and it was
• Microsoft showed off Halo: Campaign Evolved, Gears of War E-Day, Fable, and a lot more
• Some games will be console-exclusive in the future, starting with the new Gears
• Microsoft will sell a limited edition Xbox Series X25 later this year
• Xbox leadership is exploring new business models for the next console - Game Pass lost "millions" of subscribers after last year's price hikes
• Xbox Insider update adds a new way to discover mutual friends, more
• Valve says the Steam Machine and Steam Frame will ship this summer

Tips and picks

• Tip of the week: Windows 11 Field Guide is being updated to 2026 edition
• App pick of the week: Brave Origin
• RunAs Radio this week: How Machine Learning Fails with Megan Robertson
• Brown liquor pick of the week: Thy Bøg

Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell

Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly

Check out Paul's blog at thurrott.com

The Windows Weekly theme music is courtesy of Carl Franklin.

Join Club TWiT for Ad-Free Podcasts!
Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit

Sponsors:

• helixsleep.com/windows
• zscaler.com/security
• trustedtech.team/windowsweekly365

Download audio: https://pdst.fm/e/pscrb.fm/rss/p/mgln.ai/e/294/cdn.twit.tv/megaphone/ww_987/ARML6999409836.mp3

An honest, no-filter conversation about where developers actually stand with AI today. Warren Parad — CTO at Authress, AWS Community Builder, and host of Adventures in DevOps — brings a contrarian 'LLM realist' perspective grounded in daily use, while Romain nuances with enterprise customer observations and the data behind the hype. Together they explore why 93% of devs feel productive but only 4% of enterprises see results — and what separates those who benefit from those who don't. Key takeaways: • AI is a multiplier, not a magic wand — The DORA 2025 report confirms AI amplifies your existing processes. If those processes are broken, AI makes them worse faster. • Spec-driven development beats instant responses — Long-form spec-based workflows let you disengage and return, avoiding the 'TikTok-ification' of software engineering where you're always context-switching. • Sub-agent opacity is a real problem — When agents delegate to sub-agents, you lose visibility into why decisions were made. Custom agents with explicit permissions and tool access help contain the blast radius. • Greenfield work is where LLMs struggle most — LLMs excel at refactoring and targeted feature changes where engineers already know the implementation. Open-ended new projects lead to scope creep and unfinished work. • Critical thinking erosion is measurable — Microsoft/Carnegie Mellon research shows knowledge workers self-report reduced cognitive effort when using AI. The long-term implications for engineering judgment are concerning. • Governance first, tools second — Enterprises that succeed with AI spend the first month on governance, AI registries, and codifying best practices before enabling tools across teams. • Software development was never the bottleneck — Unless AI solves handoffs, knowledge management, and organizational alignment, faster coding alone won't compress your roadmap.

With Warren Parad, CTO at Authress & Host of Adventures in DevOps

Authress — Login and Access Control for B2B

Adventures in DevOps Podcast

Warren Parad — Personal Site

DORA 2025 Report

Microsoft/CMU — The Impact of Generative AI on Critical Thinking

Forgejo — Self-Hosted Git with Federation

Rig — Rust AI Framework

AWS Kiro — AI-Powered Development Environment

AWS Strands Agents SDK

Simon Wardley — Wardley Maps & PST Framework

The Phoenix Project — Gene Kim, Kevin Behr, George Spafford

The Magicians — Lev Grossman (Warren's Book Pick)

Download audio: https://op3.dev/e/dts.podtrac.com/redirect.mp3/developers.podcast.go-aws.com/media/212.mp3

Episode 0033 - Route of All Evil

Cloud networking still breaks when teams assume the platform will "just handle it," and Carl and Brandon dig into why. They challenge that myth and show where parity falls apart across providers: VNet, VPC, and VCN primitives look familiar but behave differently in defaults, region and zone design, and routing/security expectations. From there, the episode moves into foundational design pressure points such as IPv4 range planning, overlapping CIDRs, Kubernetes networking overlays, and the route-level surprises that cause hard-to-diagnose failures, including asymmetric paths, BGP mistakes, and MTU mismatches.

The second half focuses on the practical failure modes teams feel in production: SNAT exhaustion that appears as random timeouts, endpoint and DNS choices that silently change traffic paths, and egress patterns that impact both reliability and cost. Load balancing choices (Layer 4 vs Layer 7), TLS termination strategy, and cloud-specific security control models all shape the final behavior of a system. The throughline is consistent: make network intent explicit, treat egress and observability as first-class design surfaces, and standardize repeatable patterns that survive provider changes.

Links

Core Networking Concepts

• RFC 1918: Address Allocation for Private Internets
• RFC 4632: Classless Inter-domain Routing (CIDR)
• RFC 4271: Border Gateway Protocol 4 (BGP-4)
• Maximum Transmission Unit (MTU)
• Asymmetric routing

Cloud Networking and Edge Services

• Azure Front Door overview
• How Cloudflare works
• Azure Virtual Network overview
• Amazon VPC user guide
• OCI Virtual Cloud Network (VCN) overview

NAT, Private Access, and Egress

• Azure NAT Gateway
• AWS NAT Gateway
• Azure Private Endpoint overview
• Azure bandwidth pricing (egress)

Load Balancing, Security, and Operations

• Azure Load Balancer overview
• Azure Application Gateway overview
• Azure Traffic Manager overview
• Microsoft Zero Trust guidance
• Azure Network Watcher flow logs overview

Hybrid Connectivity

• AWS Direct Connect
• Azure ExpressRoute overview
• Oracle FastConnect overview

Visit us at:

• twitter.com/CloudChatTech
• discord.cloudchat.tech
• cloudchatpodcast@gmail.com
• linkedin.com/company/cloudchat

Download audio: https://traffic.libsyn.com/secure/dfd84fca-7055-4605-98ce-3b0f8cbd6e15/cc-0033.mp3?dest-id=4423448

When version 1 of the AWS Command Line Interface (AWS CLI v1) enters maintenance mode on July 15, 2026, the way its botocore and s3transfer dependencies are bundled will change. This post explains these changes and provides steps to minimize impacts on your workflows and applications. For more information about AWS CLI v1 maintenance mode, refer to the blog post CLI v1 Maintenance Mode Announcement.

Background

The AWS CLI v1 is built on top of two foundational Python libraries:

• botocore is the low-level library that provides AWS service definitions, request signing, response parsing, and retry logic. When AWS launches a new service or adds new API operations to an existing service, those changes are delivered through botocore updates.
• s3transfer is the library that manages Amazon S3 file transfers, including multipart uploads, parallel downloads, and transfer configuration. High-level S3 commands in the AWS CLI rely on s3transfer, such as aws s3 cp and aws s3 sync.

What’s happening?

Currently, each version of the AWS CLI v1 depends on specific versions of botocore and s3transfer. These dependencies are installed as separate packages. This means that upgrading the AWS CLI v1 also brings in a newer version of these packages. Starting with maintenance mode, botocore and s3transfer will be vendored (bundled and packaged directly) into the AWS CLI v1 codebase. The AWS CLI v1 will no longer rely on the standalone packages. This represents a significant shift in how dependencies are managed within the AWS CLI v1.

If you rely on automatic dependency updates when upgrading the AWS CLI v1, this behavior will change. The AWS CLI v1 will include its own internal copies of botocore and s3transfer. Updates to these internal copies will only occur when AWS releases a new version of CLI v1. Installing or upgrading the standalone botocore or s3transfer packages will have no effect on the versions used by the AWS CLI v1.

botocore and s3transfer will continue to be developed and released as separate packages, because they are also dependencies of the AWS SDK for Python (boto3). However, those standalone package updates will not affect the AWS CLI v1—the CLI will only use its own bundled copies.

How you may be affected

Upgrading the AWS CLI v1 will no longer upgrade the standalone botocore and s3transfer packages. The AWS CLI v1 will use only its own internal copies, and the standalone packages will remain at whatever version is independently installed.

If your environment has both the AWS CLI v1 and boto3 installed, they will each use their own separate copies of botocore and s3transfer. Updating either the AWS CLI or boto3 will not affect the other’s dependencies. Additionally, because the AWS CLI v1 will bundle its own copies of botocore and s3transfer alongside the standalone packages used by boto3, environments with both installed will contain two copies of these libraries.

Updates to the standalone botocore and s3transfer packages will continue as before, since they are also dependencies of boto3. However, those updates will not reach the AWS CLI v1 unless a new AWS CLI v1 version is released with updated internal copies. As described in the maintenance mode announcement, new AWS CLI v1 versions will only be released to address critical bug fixes and security issues.

Recommended actions

To stay updated with the latest AWS services and features, we recommend that you migrate to AWS CLI v2. To learn more about transitioning to AWS CLI v2, refer to the Migration guide for the AWS CLI version 2. Additionally, verify if your workflows rely on botocore or s3transfer brought into your environment via the AWS CLI v1. If you have other applications in the same environment that consume them, you may need to explicitly pin their dependency versions. Be sure to validate your existing scripts and automation with the new maintenance mode releases. Last, monitor the AWS CLI changelog to stay informed about new AWS CLI v1 versions and vendored dependency updates.

Conclusion

As the AWS CLI v1 enters maintenance mode on July 15, 2026, the botocore and s3transfer dependencies will be vendored, which may affect your workflows and scripts. While the CLI v1 will continue to receive critical updates, we encourage you to migrate to AWS CLI v2 for the latest features and improvements.

Feedback

If you need migration assistance or have feedback, reach out to your usual AWS support contacts. You can also open an issue on GitHub. Thank you for using the AWS CLI!