Hacker News new | past | comments | ask | show | jobs | submit
A big part of reviewing code to me now is just maintaining my mental model of how the system works and why so I can continue to write good prompts to evolve it. Also checking for various brittle and architecturally unaligned smells; it's more of a skim to stimulate questions for filling gaps in my mental model and to find and fix smells.

I think of clankers as "lossy intention amplification and reprojection devices with hopefully tasteful distortion." Whether they're amplifying and reprojecting our intentions into code or a bunch of assumptions in some specification document, I think the problems are the same: if we stop even skimming the code at some point, it will still need to serve a purpose valuable to humans to be worth anything. It's kind of like getting a device that can answer the ultimate question of life, the universe and everything: you still need to know what questions to ask it.