I’m a productive programmer with a memory of a fruit fly
I have the same problem (i.e. terrible short-term memory, though my long-term memory is fine), and I&#x27;ve picked up a number of compensating behaviors over the years. By far, <i>documentation</i> is my #1 go-to strategy. I document code extensively, even if I&#x27;m the only person who is ever going to read it again. People have mocked me for this, but I believe it&#x27;s a superpower.<p>Most programmers believe a number of blatant falsehoods about documentation, with the most prevalent being &quot;comments go out of date quickly, so there&#x27;s no point in investing in them&quot;. Maybe I&#x27;m just hyper-aware of it because my short-term memory sucks, but code comments have saved me on so many occasions that they&#x27;re simply not optional.<p>You <i>can</i> document your code. You <i>can</i> keep it up to date. It isn&#x27;t that hard. You just don&#x27;t want to.