Towards Data Science

Context Rot: Why Claude Code Sessions Decay, and How to Govern Them

Long sessions rot quietly, well before any token limit is reached. Here’s why, and how to govern your context in Claude Code.

Towards Data Science
Aug 30

Context Engineering Is Changing. Here’s What It Means for Data Scientists

The article discusses how context engineering is evolving and outlines practical ways data scientists can incorporate the newest guidelines into their everyday work. It explains the importance of adapting to these changes to improve model performance and relevance. The piece offers actionable steps for integrating context engineering into typical data science workflows.

By Piero Paialunga
Towards Data Science
Aug 24

AI Agents Don’t Need More Context — They Need Typed Context

The article argues that AI agents face a context typing issue rather than merely a lack of context. It explains how flattening instructions, memory, evidence, and tool outputs into a single string erases semantic boundaries, and presents a lightweight, zero‑dependency Python runtime that preserves these boundaries, tracks provenance, and rejects invalid transformations before they reach the model. The post details the implementation, testing, and the guarantees and limitations of this approach.

By Emmimal P Alexander
Towards Data Science
Aug 29

When to Use Claude Code and When to Use Codex

The article discusses the appropriate contexts for using Claude Code versus Codex, two coding agents. It explains the strengths and ideal use cases for each tool, helping readers decide which agent to employ for specific programming tasks. The post provides guidance on selecting the most suitable coding assistant based on the nature of the work.

By Eivind Kjosbakken
Towards Data Science
Aug 28

Why Claude Code Time Estimates Are Poor

The article titled "Why Claude Code Time Estimates Are Poor" discusses the challenges and shortcomings of using Claude, an LLM, for estimating code development time. It highlights how these estimates can be unreliable and offers insights into improving communication when working with LLM programming tools.

By Eivind Kjosbakken