AI-READABLE CODE
Naming in software goes way beyond any aesthetics. Good naming minimizes reconstruction work. Here is the style and habits that I've picked up.
ADAM TORNHILL
JUN 23, 2026
Today we’re taking on the second hardest problem in computer science: naming.
Each time we write code, we face a multitude of micro-decisions. How do we label functions, classes, variables, etc. to get the most out of the code as a communication medium? That is, communication that sharpens our thoughts in the moment, as well as code that supports our future selves and any agent trying to make sense of what’s already there.
As such, naming in software goes way beyond any aesthetics. Good naming minimizes reconstruction work. For both humans and machines.
In this article, I share the style and habits that I’ve picked up. It’s a style that evolved over the years, and shaped by viewing software through the lens of cognitive psychology to support the way we think, reason, and solve problems
In this video I analyze the DOOM project by id Software.
Comment, like, subscribe, let’s trigger the algo!
The focus will be on software architecture, technical limitations, technical concepts.
If you like the content comment, like and subscribe to support the channel!
- 00:00 DOOM
- 03:18 Software Architecture
- 08:06 Build Process
- 10:04 Component Diagram
- 11:07 WAD Files
- 13:20 Main Loop
- 14:35 2D Renderer
- 20:45 3D Renderer Intro
- 24:22 Binary Space Partitioning
- 27:45 BSP Example
- 31:03 Player FOV
- 35:22 Wall Clipping
- 40:30 Visplanes
- 41:25 "Masked"
- 42:21 Conclusion and Lessons