22 May 2026
Yielding to Claude's limits & Google I/O
From a single yield keyword that saves megabytes of memory, through a lawsuit dismissed in 90 minutes, to 900 million users — here is what is worth your attention this week.
Hello,
Three posts this week — one to finish a series, one to answer a question I keep getting asked, and one to make sense of a very loud two days in AI. Here they are.
Python Generators and Iterators: Lazy Birds https://daehnhardt.com/blog/2026/05/20/python-generators-iterators/
This is the sixth and final post in the Python Basics series, and the one I was looking forward to most. Generators are the feature that, once you understand them, you start seeing everywhere — and wonder how you managed without them. The idea is beautifully simple: much like putting off doing the washing up until you desperately need a single clean mug, instead of computing an entire sequence up front and holding it in memory, you yield one value at a time, only when it is actually needed.
A list of a million items costs eight megabytes; a generator producing the same million items costs two hundred bytes. The post covers generator expressions, infinite sequences, itertools, and finishes with a complete lazy pipeline for processing a stream of bird sightings — which, yes, is exactly as pleasant to write as it sounds.
Claude Free Tier Limits: What Breaks First and What Pro Fixes https://daehnhardt.com/blog/2026/05/21/claude-pro-vs-free/
The question I am asked most often about Claude is: is Pro worth it? The honest answer is that it depends entirely on which limits you are hitting — and they break in a specific order. The post walks through all four: message limits, the absence of persistent context, the missing terminal tool for developers, and the deep research mode that most people only notice when a task actually demands it.
It also covers Opus 4.7, Projects, Cowork, and a practical table of token-saving strategies for both claude.ai subscribers and API users. I wrote it while editing it with Claude Pro, hit the limit before finishing, and left that detail in — because it is a far more useful illustration than anything I could have constructed deliberately.
Google I/O 2026: 900M Users, Musk Loses, Gemma Ships https://daehnhardt.com/blog/2026/05/22/google-io-2026-900m-musk-loses-gemma-ships/
Google I/O ran on 19 and 20 May and was, by any measure, the most AI-dense developer conference Google has run. Gemini 3.5 Flash shipped generally available on the day it was announced, and Antigravity 2.0 became a full agent development platform with parallel subagent execution. Meanwhile, AI Search — redesigned for the first time in 25 years — crossed one billion monthly users.
On the exact same day, a jury in Oakland took just 90 minutes to throw out Elon Musk’s $150 billion lawsuit against OpenAI on statute of limitations grounds. The substantive question about OpenAI’s mission was never answered and will inevitably surface again. Cheekily, Anthropic scheduled Code with Claude London for the exact same day as the I/O keynote, which tells you everything about where the real competition is being fought right now: not on benchmarks, but on developer mindshare.
That is it for this week. As always, let me know what you think — and whether any of it was useful.
Elena
Enjoyed this? Get more like it.
Weekly notes on AI tools, Python, and what I'm actually building — plus two free gifts: the 15-page Fantastic AI: The 2026 Toolkit and a Git Commands & Contribution Workflow Cheatsheet.