I read a lot. Too much, but what can you do? At the end of each workday, I publish a list of every tech-related article or blog I read that day. And I’ll sometimes mix in a YouTube video or code repo for fun.
If you’d like a shortcut to keep up with what’s happening in our industry, consider subscribing via RSS, browser bookmark, or via email:
Here are the last few editions:
- Daily Reading List – May 8, 2026 (#780)Today’s links look at what happens if you give in to Cognitive Surrender with AI, why the ‘AI Job Apocalypse’ is complete fantasy, and what it means to have write-only code coming out of your AI workflow.
- Daily Reading List – May 7, 2026 (#779)Today’s links look at why SaaS freemium playbooks don’t work in AI, how to design front-end systems for cloud failure, and why coding with AI agents is a baseline expectations for tech managers.
- Daily Reading List – May 6, 2026 (#778)Today’s links look at how to be direct AND strategic in communication, how to design an AI-native engineering org, and why you improve AI agents through better evals.
- Daily Reading List – May 5, 2026 (#777)Today’s links look at what happens when 1500 agents hit production at Uber, what a map of system topologies looks like, and how AI is finding 20-year-old bugs in mature software.
- Daily Reading List – May 4, 2026 (#776)Today’s links look at why startups are choosing Flutter in 2026, how to run multiple coding agents safely with git worktrees, and why your pull requests are still too big.