Pro tip: Keep a log of your work in a text file. I write a few bullet points for each day and on Friday write a “Next Week” section for my todos on that following Monday. Helps reduce the cognitive load of trying to remember what the hell you were about to do next.
// TODO make this work
Pro tip: Keep a log of your work in a text file. I write a few bullet points for each day and on Friday write a “Next Week” section for my todos on that following Monday. Helps reduce the cognitive load of trying to remember what the hell you were about to do next.
I write down my current/next thoughts on a Post-It and stick it to my keyboard for Monday Noodle.
I actually enjoy this part, where I’ve written some intricate code of sorts and get to spend some time writing a memo that explains how it works.
I usually don’t even end up reading them, because the process of writing a good memo will make me remember it.
I sort of do this in a block comment at the top of some scripts I write.
Changelog for Completed Stuff and Future Features for todo
AKA a WAR, which is an unnecessarily aggressive acronym for “weekly action report.”
“Weekly action report!? Oh, that means war for sure”
Make jar, not war
I’d rather write a WAR than write Java, TBH.
Jeekly activity report?