Best of your X follows: code power tools, AI jobs, and bot replies
Today's digest tracks five original X posts on Claude transcript links failing inside Claude Code, stronger code generation helping expert programmers more, AI's labor-market impact, bot-reply sameness, and algorithmic routing as a city-level lever.
A thin but useful window: five original posts cleared the bar, and they all point at systems that are awkward at the edges. Claude links do not open inside Claude Code. Code generation now rewards stronger programmers more than weaker ones. AI may be creating jobs before it removes them. X replies are converging into the same bot-shaped answer. Even routing 2% of cars differently can change city traffic.
Coverage window: July 11, 2026 18:00 through July 12, 2026 18:00 UTC. Pure reposts, small talk, off-topic posts, and context-light reactions were excluded.
| Item | Source type | Time signal | Why it made the cut |
|---|---|---|---|
| Claude transcript links | X | July 12, 15:47 | Simon Willison spotted a practical product seam: Anthropic's anti-scraping defenses can block its own coding tool from reading shared Claude transcripts 1 |
| Code gen as a power tool | X | July 12, 14:20 | François Chollet framed the new coding-agent baseline as a reversal: strong programmers now benefit most 2 |
| AI and jobs | X | July 11, 20:12 | Sam Altman said AI has been net job-creating so far, while leaving the claim as a provisional read rather than a certainty 3 |
| Bot-reply sameness | X | July 12, 14:23 | Ethan Mollick proposed ranking replies by semantic distance, not just engagement, to fight same-shaped bot answers 4 |
| Google Maps routing | X | July 12, 14:04 | Mollick pointed to a small routing intervention with a city-scale effect: 2% of cars choosing equally fast, less-congested routes 5 |
AI tools and developer workflows
Simon Willison: Claude cannot always read Claude
Author context: Simon Willison's profile identifies him as creator of Datasette and co-creator of Django 1.
Why it made the cut: this is not a launch announcement. It is a product-integration failure that developers will recognize. Willison wrote that a shared Claude transcript link cannot be pasted into Claude Code because Anthropic's anti-scraping measure prevents its own tool from accessing another Anthropic tool's output 1. At capture, the post had 128 likes, 29 replies, 5 reposts, 9 bookmarks, and 10,745 views 1.
Three-line read:
- The problem is not model quality; it is tool-to-tool handoff inside the same vendor ecosystem 1.
- Anti-scraping controls can protect public pages while breaking legitimate agent workflows.
- If coding assistants are meant to work across saved conversations, vendors need permissioned handoff paths, not brittle web scraping.
Willison's original post is the whole issue in one sentence:
コンテンツカードを読み込んでいます…
François Chollet: code gen flipped from crutch to power tool
Author context: François Chollet's profile identifies him as co-founder of NDEA and ARC Prize, creator of Keras and ARC-AGI, and author of Deep Learning with Python 2.
Why it made the cut: it sharpens yesterday's broad agentic-coding theme into a more useful claim. Chollet argued that weak AI code generation mostly helped low-skill programmers by raising the floor, while current stronger code generation is most useful to high-skill programmers. His summary: it went from a crutch to a power tool 2. At capture, the post had 765 likes, 63 replies, 59 reposts, 163 bookmarks, and 54,081 views 2.
Three-line read:
- The claim is about who captures value: stronger programmers can steer, review, and compound model output better 2.
- Lower-skill users may be underusing the tool or getting buried by output they cannot evaluate.
- For teams, the bottleneck shifts toward taste, review discipline, and knowing what to ask for.
The post is worth reading because it avoids vague productivity talk:
コンテンツカードを読み込んでいます…
AI and labor-market narratives
Sam Altman: AI may be creating jobs so far
Author context: Sam Altman's public profile is terse, but he is posting from a verified account and is OpenAI's CEO; the post itself carries the claim, not a supporting labor dataset 3.
Why it made the cut: the wording is careful enough to be useful. Altman wrote that AI has been "net job-creating" so far, adding that this was not what he expected and that the direction may continue 3. At capture, the post had 11,948 likes, 1,679 replies, 451 reposts, 1,103 bookmarks, and 1,852,237 views 3.
Three-line read:
- The important hedge is "so far"; this is a directional claim, not proof that displacement risk is gone 3.
- The useful question is whether AI creates enough new work around integration, review, security, and product design to offset tasks it automates.
- Treat it as a CEO thesis to watch against hiring data, not as a settled labor-market result.
Here is the original claim and its hedging:
コンテンツカードを読み込んでいます…
Platform quality and algorithmic systems
Ethan Mollick: bot replies need semantic diversity, not more sameness
Author context: Ethan Mollick's profile identifies him as a Wharton professor studying AI, innovation, and startups 4.
Why it made the cut: this is a concrete product proposal for a noisy platform problem. Mollick wrote that X's bot-reply problem may be unsolvable as currently designed; his proposal is to measure semantic distance in latent space and surface replies that offer actual variation 4. At capture, the post had 356 likes, 45 replies, 8 reposts, 20 bookmarks, and 21,075 views 4.
Three-line read:
- The complaint is not only that replies sound AI-written; it is that many replies make the same point 4.
- Ranking by semantic distance would reward novelty in the reply set, not just engagement.
- The hard part is abuse: attackers could learn to optimize for novelty just as they optimized for visibility.
Mollick's proposal is short and specific:
コンテンツカードを読み込んでいます…
Ethan Mollick: route 2% of cars differently, move the whole city
Author context: same source as above: Mollick's profile identifies him as a Wharton professor studying AI, innovation, and startups 5.
Why it made the cut: it is not an AI post, but it fits the channel's systems-and-software filter. Mollick wrote that when Google changed routing for 2% of cars using Google Maps toward equally fast routes that avoided congested areas, speeds increased and fuel consumption fell across the city 5. At capture, the post had 786 likes, 33 replies, 41 reposts, 127 bookmarks, and 63,034 views 5.
Three-line read:
- The lever is small: only 2% of routed cars changed behavior in the example Mollick cited 5.
- The effect is system-wide because route choices are coupled; one driver's path changes congestion for others.
- For AI product builders, it is a reminder that recommendation systems can shape shared infrastructure, not just individual preferences.
The original post is the cleanest statement of the example:
コンテンツカードを読み込んでいます…
関連コンテンツ
- ログインするとコメントできます。
More from this channel
- Best of your X follows: live assistants, bioresilience, and frontendmaxxing
- Best of your X follows: agent habits, research bottlenecks, and anti-slop taste
- Best of your X follows: cache-friendly uvx, Canadian research, and agent UX
- Best of your X follows: Morpheus, Sol builds, and AI roadmaps
- Best of your X follows: AI employees, bio bounty, and Deep Time
- Thin X day: Fable guardrails, AI tutors, and Runloom
- Best of your X follows: Sol, GPT-Live, and product clarity
- Best of your X follows: Fable prose, MTurk, and model workspaces