- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
I secretly have forgotten a lot of the working code I wrote months ago; and whenever someone asks, I need to go back and read it like new
// 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 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.
AKA a WAR, which is an unnecessarily aggressive acronym for “weekly action report.”
“Weekly action report!? Oh, that means war for sure”
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
I write down my current/next thoughts on a Post-It and stick it to my keyboard for Monday Noodle.
Monday stand-ups are the worst
Its always like 3 hours to remember why I was doing what I was doing, just to scrap it because the core is all wrong.
Make up something quickly stand-up is only 30 minutes after starting time
As is tradition.
If only there were some way to leave some sort of … what’s it called a comment maybe 🤔 idk…
/s
/* look I know this sucks ass but its Friday and I want to go home. I'll fix it on Monday. */
Last committed 2014.
Me except it’s everyday, and it’s my boss’s code, so I’m not able to complain 🫠
You can always complain. You’re complaining right now.
But I’m smart enough not to do it to my boss.
Or are you? Try it, just a lil 😼
Me coming back to my run of ‘luck be a landlord’ and trying to figure out what strategy I was even thinking of, when I witness the chaos I left myself as I press ‘continue’…
This is so me!