Live data from Hacker News

Cognitive Debt: When Velocity Exceeds Comprehension

rockoder.com

121–130 of 234 posts

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#121
> The second is absorption: mental models form, edge cases become intuitive, architectural relationships solidify into understanding. ... . The friction of implementation creates space for reasoning.

> This gap between output velocity and comprehension velocity is cognitive debt.

I have felt that lack of absorption during the last months, adding doomscroolling to the equation, I have felt how my thinking is disappearing.

I tried to speculatively expand that idea in this post

https://news.ycombinator.com/item?id=47186004

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#122
You get the same when your company employs a lot of low to medium skilled offshore devs. Every morning or every week you get a huge pile of code that sort of works but there is simply no way to review it in a meaningful way. It's just too much. Thats how I feel working with Claude Code. It cranks out a lot of code really quickly but how do I know it's not creating subtle problems?

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#123

The article very much resonates with my experience past several months. The project I work on has been steadily growing for years, but the amount of engineers taking care of it stayed same or even declined a bit. Most of features are isolated and left untouched for months unless something comes up. So far, I managed growing scope by relying on tests more and more. Then I switched to exclusively developing against a s…

Learning has always been to write things down. Just reading it seldom sticks.

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#124
I know the topic won't probably be about this -and I'll be reading the article next-, just wanted to share that this title perfectly reminded me the feeling of attempting the speed reading technique explained in this old gem of a video (minute 20:15)

BOOKSTORES: How to Read More Books in the Golden Age of Content

https://m.youtube.com/watch?v=lIW5jBrrsS0&t=1215s

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#125

Richard Gabriel wrote a famous essay Worse Is Better ( https://www.dreamsongs.com/WorseIsBetter.html ). The MIT approach vs the New Jersey approach does not necessarily apply to the discussion of the merits of coding agent, but the essay's philosophy seems relevant. AI coding sometimes sacrifices correctness or cleanness for simplicity, but it will win and win big as long as the produced code works per its users' sta…

I hope people can ask themselves why the goal is "winning" and "winning big", and not making a product that you are proud of. It shouldn't be about VC funding and making money, shouldn't we all be making software to make the world a little bit better? I realize we live in an unfortunate reality surrounded by capitalism, but giving in to that seems shortsighted and dismissive of actual problems.

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#126

I think we might as well just go all in at this point: "LGTM, LLM". The industry always overshoots and then self-corrects later. Therefore, maybe the right thing to do is help it get to a more sane equilibrium is to forget about the code altogether and focus on other ways to constrain it / ensure correctness and/or determine better ways to know when comprehension is needed vs optional. What I don't like is the imposs…

yep, as is always the case, it has to break before you can fix it. Bandaiding something along just makes it more painful for longer.

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#128

I think we might as well just go all in at this point: "LGTM, LLM". The industry always overshoots and then self-corrects later. Therefore, maybe the right thing to do is help it get to a more sane equilibrium is to forget about the code altogether and focus on other ways to constrain it / ensure correctness and/or determine better ways to know when comprehension is needed vs optional. What I don't like is the imposs…

While I too am only seeing a boost on the order of 20% so far, I think there are more creative applications of LLM beyond writing code, that can unlock multiples of net productivity in delivering product end to end. People are discovering these today and blogging about them, but the noise about dark factories and agents supervising agents supervising agents, etc, is drowning out their voices. Every one of us is a pio…

Yes exactly, of all the uses cases for LLMs "writing code" is easily my least favorite. Theres so many other cool things for "stochastic contextual orchestrators"

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#129
post #53
post #9

The whole premise of the post, that coders remember what and why they wrote things from 6 months ago, is flawed. We've always had the problem that understanding while writing code is easier than understanding code you've written. This is why, in the pre-AI era, Joel Spolsky wrote: "It's harder to read code than to write it."

I don't remember exactly what I wrote and how the logic works, but I generally remember the broad flow of how things tie together, which makes it easier to drop in on some aspect and understand where it is code-wise.

There's code structure but then there's also code philosophy.

The worst code bases I have to deal with have either no philosophy or a dozen competing and incompatible philosophies.

The best are (obviously) written in my battle tested and ultra refined philosophy developed over the last ~25 years.

But I'm perfectly happy to be working in code bases written even with philosophies that I violently disagree with. Just as long as the singular (or at least compatible) philosophy has a certain maturity and consistency to it.

Re: Cognitive Debt: When Velocity Exceeds Comprehension

#130
post #97

Earlier quoted context omitted.

I think that recording dialog with the agent (prompt, the agent's plan, and agent's report after implementation) will become increasingly important in the future.

I have this at the bottom of my AGENTS.md: You will also add a markdown file to the changelog directory named with the current date and time `date -u +"%Y-%m-%dT%H-%M-%SZ"`, record the prompt, and a brief summary of what changes you made, this should be the same summary you gave the developer in the chat. From that I get the prompt and the summary for each change. It's not perfect but it at least adds some context ar…

How often is it the same summary given to the developer in the chat?
Post reply on HN