This article is about standardisation, particularly how it relates to understanding code. I’ll first go into an historical example that highlights the lack of standardisation in an area where we take it for granted today. After that I’ll get into code, and how understanding code is like understanding data via visualisations. In both the historic … Continue reading Standardisation and code
Coding After Coders: The End of Computer Programming as We Know It - …
archived 16 Mar 2026 15:14:04 UTC
The Definitive Guide to Understand Anything: Turning Code and Knowledge Into Graphs That Teach
You just joined a new team. The codebase is 200,000 lines of code. The original authors left a year ago. The documentation is a wiki last…
Scaling Monosemanticity: Extracting Interpretable Features from Claude 3 Sonnet
We find a diversity of highly abstract features. They both respond to and behaviorally cause abstract behaviors. Examples of features we find include features for famous people, features for countries and cities, and features tracking type signatures in code. Many features are multilingual (responding to the same concept across languages) and multimodal (responding to the same concept in both text and images), as well as encompassing both abstract and concrete instantiations of the same idea (such as code with security vulnerabilities, and abstract discussion of security vulnerabilities).
Its Time for a New Programming Language
Today, when compared to any other point in programming history, we find ourselves spoiled for choice when it comes to programming…
Sourcegraph — Code Understanding, Oversight and Evolution
Give humans and agents complete context to understand, oversee, and evolve the world's largest, most complex codebases.
Code Is Cheap Now, And That Changes Everything | Pere Villega
AI coding agents have made code production nearly free. Drawing on insights from Kent Beck, Paul Ford, and Simon Willison, this post argues that the value has shifted from writing code to defining systems — contracts, invariants, SLAs, and verification.
What I Found Interesting in Claude Code's Source
A breakdown of the most interesting engineering patterns in Claude Code's leaked source code: composable system prompts, runtime instruction injection, context compression, forking, prompt caching architecture, and more.
Reports of code's death are greatly exaggerated
A sufficiently detailed spec is code begins with this lovely comic:
Something Pretty Right: A History of Visual Basic | Retool
How Visual Basic became the world’s most dominant programming environment, its sudden fall from grace, and why its influence is still shaping the future of software development.
Auto-grading decade-old Hacker News discussions with hindsight
A vibe coding thought exercise on what it might look like for LLMs to scour human historical data at scale and in retrospect.
Introduction - Standard.site
A brief introduction to Standard.site lexicons, what they are, and how they're used.
LLMs as Collaborators in Language Specification and Design (PLSS 2026) - SPLASH/ISSTA 2026
Workshop on Programming Language Standardization and Specification This workshop aims to foster cross-pollination between researchers and industry professionals with experience in programming language specification and standardization. It provides a forum where participants can share insights, case studies, and best practices, and collaboratively explore solutions to current challenges. The goal of the workshop is to improve the collective understanding of how programming languages are specified, standardized, and evolved in practice. The workshop examines specifications as the foundation ...
W Social and the ancient art of neighbourliness - We Can Just Do Things
Good behaviour matters more than good code
W Social and the ancient art of neighbourliness - We Can Just Do Things
Good behaviour matters more than good code