Cognitive Debt: When Velocity Exceeds Comprehension
1–10 of 234 posts
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#2This thread is closely related: https://news.ycombinator.com/item?id=47194847
"The right amount of AI is not zero. And it’s not maximum."
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#3It feels like it's Saturday and HN is full of scared blog posts.
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#4The organizational memory and on-call debugging sections allude to this, but there are significant effects on other parts of the organization. For example, if I work in product support and a customers asks about a products behavior - it becomes much more challenging to find answers if documentation is sparse (or ai written), engineers don’t immediately know the basics of the code they wrote, etc. Even if documentation is great and engineers can discuss their code, the pace of shipping updates can be a huge challenge for other teams to keep up with.
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#5This thread is closely related: https://news.ycombinator.com/item?id=47194847 "The right amount of AI is not zero. And it’s not maximum."
Author from the other thread here. I'm surprised to see so many similarities, but in good faith I'll assume that it's just a coincidence because many devs start to notice the upcoming problems.
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#6I have been in a big company for 4 years, and following the zillions of projets going on here and there, how they interact [nicely or not] has become a job in itself.
Very disturbing as I thought my technical skills would help me clarify the global picture. And that is exactly the contrary that is happening.
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#7Sometimes you have to go slow to go fast.
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#8Skill is stored in the fingers!
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#9The 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."
Re: Cognitive Debt: When Velocity Exceeds Comprehension
#10Sometimes you have to go slow to go fast.
"Slow is smooth, and smooth is fast."