Re:Cognitive Debt: When Velocity Exceeds Comprehension
by senko on Saturday February 28, 2026 @11:38AM
(#47197360)
[delayed]
[ Parent
| on HN ]
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by copperx on Saturday February 28, 2026 @12:09PM
(#47197698)
Lucky you. I always go "huh, so I wrote this?". And this was in the pre-AI era.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by seba_dos1 on Saturday February 28, 2026 @12:16PM
(#47197781)
These feelings aren't mutually exclusive. I'm often like "I have no memory of this place" while my name stares at me from git blame, but that doesn't mean my intuition of how it's structured isn't highly likely to be right in such cases.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by datsci_est_2015 on Saturday February 28, 2026 @01:24PM
(#47198575)
Like a painter not remembering a specific stroke, but being able to recreate it instantly because of years of muscle memory.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by layer8 on Saturday February 28, 2026 @03:02PM
(#47199582)
There is probably a bias here, because you notice the times where the code is unfamiliar more than the times when it’s still familiar. You wouldn’t go “huh” if not remembering was the normal case. If it were, you’d rather go “huh” if exceptionally you do remember.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by suzzer99 on Saturday February 28, 2026 @02:25PM
(#47199185)
It feels like that at first, especially as I get older. But I still think it comes back to me a lot quicker if I once understood it than if I was learning it from scratch. Possibly just because I know how I think.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by SoftTalker on Saturday February 28, 2026 @12:14PM
(#47197751)
I find this to be the case if it was something I was deeply involved with.
Other times, I can make a small change to something that doesn't require much time, and once it's tested and committed, I quickly lose any memory of even having done it.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by senko on Saturday February 28, 2026 @12:25PM
(#47197884)
Yeah I did pour a lot of sweat and thinking into that codebase all those years ago.
When I do a drive-by edit, I probably don't remember it in a week.
Which is why the "cognitive debt" from the article is relevant, IMHO. If I just thoroughly review the plan and quickly scan the resulting code, will that have a strong enough imprint on my mind over time?
I would like to think "yes", my gut is telling me "no". IMHO the LLMs are now "good enough" for coding. These are hard questions we'll have to grapple with this in the next year or two (in context of AI-assisted software development).
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by vjvjvjvjghv on Saturday February 28, 2026 @01:31PM
(#47198640)
I definitely understand my own code better than what other people wrote, even from 10 years ago. I often see code and think "this makes sense to do it this way". Turns out I wrote it years ago.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by layer8 on Saturday February 28, 2026 @03:07PM
(#47199634)
That means your personal growth has plateaued. ;)
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by vjvjvjvjghv on Saturday February 28, 2026 @04:50PM
(#47200662)
My coding style definitely has plateaued. It probably even has regressed to preferring simpler code.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by softboyled on Saturday February 28, 2026 @05:37PM
(#47201090)
But that's not a regression...
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by Jensson on Saturday February 28, 2026 @06:27PM
(#47201634)
And always thinking your code from a year ago is shit means the code you write right now is also shit, so you never get good.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by vjvjvjvjghv on Saturday February 28, 2026 @09:54PM
(#47203153)
That's the correct attitude.