AI companies keep destroying old books. Heres why.
THE SO WHAT
Physically slicing up old books for training data makes the IP and provenance problem tangible — cultural institutions now sit directly in the AI supply chain. If you depend on third-party data, expect tighter access, higher licensing costs, and more scrutiny on how your models were fed.
READ THE SOURCE
MORE FROM THE WIRE
I’m a software developer, and AI has changed my job in 3 major ways
Developer roles are stretching horizontally — AI handles more of the boilerplate, so the human job shifts toward architecture, cross-team glue, and higher-stakes review. If you run an engineering org, your bottleneck is no longer lines of code but how quickly your best people can safely supervise and integrate AI-generated work.
Applied AII asked ChatGPT, Claude, Gemini and Grok which sci-fi AI they're most like — and their answers were surprisingly different
How different models map themselves to sci-fi AIs is less about capability and more about brand positioning and guardrail choices. For builders, it’s a reminder that model ‘personality’ is now a product surface you can and should design intentionally for your domain.
Applied AIAnthropic announces a feature that allows different Claude Code sessions to message each other with updates and other information, available on macOS and Linux
Claude Code sessions messaging each other is a small but clear move toward multi-agent dev environments — where your “projects” coordinate autonomously across terminals. Teams building internal tools should start assuming agent-to-agent communication as a primitive and design logs, permissions, and review flows accordingly.
AI was meant to replace software developers. It's creating more instead.
Atlassian’s numbers pointing to more, not fewer, software builders is the classic automation pattern — lower unit cost expands demand and surface area. If you run product or eng, plan for AI to change your skill mix and throughput expectations, not your headcount overnight.