The context · May 2025
Anthropic released Claude Opus 4 and Sonnet 4 in May 2025, presenting improvements in coding and extended work with tools. [1]
A proposed project brief inspired by the period’s developments. This is an idea for exploration, not an announced Sansa product, an approved roadmap or a claim of completed client work.
Pick a source of repeated friction
Choose a module that regularly slows changes, such as a brittle import routine or a duplicated validation path. Document its current inputs, outputs and known edge cases. Confirm which observed behaviours are intentional before changing the structure.
Separate understanding from rewriting
First map the module’s callers and write checks for the behaviours that matter. Then make the smallest structural improvement that addresses the problem. Review the patch with the team who will maintain it. Avoid combining a major dependency upgrade with a behavioural change unless the dependency is essential.
Define the handover
The proposed outcome is a maintained module, relevant regression checks and a brief explanation of the new boundaries. Release with a recovery path and observe the affected workflow. Judge the project by reduced maintenance friction and preserved behaviour, not by how much of the original code was replaced.
Source & context
Anthropic · Claude 4, 22 May 2025This retrospective was written for the archive in September 2026. The linked primary source documents the announcement or event; the practical interpretation and proposed approach are Sansa’s editorial perspective. Public examples do not imply a client relationship. Product capabilities and guidance may have changed since the period discussed.
Another perspective · May 2025
Longer-running coding work needs shorter checkpoints
Continue readingWorking through a similar question?
Talk it through with Sansa