Re:Cognitive Debt: When Velocity Exceeds Comprehension
by matsemann on Saturday February 28, 2026 @01:40PM
(#47198749)
Learning has always been to write things down. Just reading it seldom sticks.
[ Parent
| on HN ]
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by RealityVoid on Saturday February 28, 2026 @02:36PM
(#47199294)
Absolutely not. Learning has been to experiment with the things until you form a effective mental model of the thing. Writing things does ab-so-luetely nothing except make you feel good in the moment. Just like listening to a lecture without engaging with the subject matter deeper.
Writing things down is important for organisational persistence of information but that is something else.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by direwolf20 on Saturday February 28, 2026 @02:43PM
(#47199351)
Writing is better than reading, but doing is better than writing.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by shimman on Saturday February 28, 2026 @02:45PM
(#47199375)
How does this apply to coding when the act of writing IS doing? Or do you mean like coding "on your own" versus following a tutorial for example?
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by coldtea on Saturday February 28, 2026 @03:13PM
(#47199710)
Means writing code (doing) vs writing documentation / plans / project architecture documents and so on.
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by direwolf20 on Saturday February 28, 2026 @02:58PM
(#47199528)
Writing code is doing
Re:Cognitive Debt: When Velocity Exceeds Comprehension
by matsemann on Sunday March 01, 2026 @02:00AM
(#47204367)
Choosing what to write down is making a mental model, extracting the core and thinking about the subject.
Seems to me you're just a bad note-taker that blindly writes things down, and for some reason decided to use that lack of knowledge in a tirade against me..