Every Friday I take 2 min to write a detailed note for the future me so I remember what I was doing. No matter how simple the task was.
That’s cheating! Guards! Arrest this filthy impostor!
Every Friday I think that I should do this for my benefit on Monday, and then immediately forget the thought and log off
Depending on how complex it could be as short as two sentences or just bullet points. Just enough to kick start my memory.
You expect me to actually comment my code?
Not even your code. He’s expecting you to comment your life.
Not code. I keep a text file “work_log.txt” on my desktop that has the date and what I worked on that day. Useful for scrum too.
Today’s:
-
Finished the modal
-
Solved the swallowing of the exception with parsing errors
-
Next: Review modal code and test
-
No Mr. Bond, I expect you to panic in the Monday morning stand-up meeting.
Yup. “finished this, start on this next week”
Usually less than two complete sentences. I find this more important with personal projects that I may not pick up in a few weeks
This is the way.
I’m not really a programmer but when I code something at work to make my job easier and I have to go before I finish it, I write a little comment for my future self to explain how I’m thinking at the moment, to help restore the flow.
Usually it doesn’t work. :-D
You didn’t have to explain you aren’t really a programmer.
Saying you write comments implies it.
My code’s self documenting I swear
My comment is self-documenting, I swear!
Because my work tends to have me working on a wide variety of features, and thus operating on vastly different parts of the codebase, I make it a point to comment out every change I make complete with the ticket that requested the change, and what the intended effect of the change is.
Cue me returning to piece of code I made (after the inevitable bug has arisen) and me staring at my own code changes in bewilderment, wondering what past me really wanted to do. Hahaha!
Now you can try to get chatgpt to explain what it does. Or Facebooks code llama.
Sometimes working at something for long enough puts you into like a fugue state. It’s like the opposite of “flow” where you just dumb down.
^This happens to me only when I had entered my dumbzone the previous shift
Happens. Then you come back to it after a few days and all the shitfuckery of last session becomes so damn obvious.
I’ve done this so many times at school and work. It’s crazy what you can accomplish by leaving a problem until the morning.
Tunnel vision. I get this all the time. Actually more beneficial to go for a walk and not work.
You very well could have substituted “Monday” with “after lunch.”
I stg sometimes conversations with my coworkers will give me memento disease and I have to go on a hunt for clues I lefy myself to figure out what I was working on 5 mins ago.
Yeah, task interruptions and task switching is awful for productivity. That’s why I love WFH and will never voluntarily go back to the office.
This comment needs more upvotes.
Opening a repository for the first time in months.
Which brainless moron wrote this idiotic code?
Runs blame.
Oh, it was me.
Fuck, I’ll look at code I wrote like a month ago and be like, “what was I thinking?”. So I try to fix it, run into some stupid issue and be like, “oh, right.”
And this is why comments are useful on code who’s purpose or reasoning isn’t super obvious or even looks counter intuitive.
A professor used to say, we don’t write code for the machine. The machine doesn’t need code. It would be just as happy whether we hand carve 1s and 0s on ferromagnetic disks or if we wrote a compiler for emojis. Binary is binary. We write code for the humans. So make it legible.
But at the same time you can over comment. If your variables are self described it’s not needed.
I never said anything about comments. My professor advocated that the code should tell yourself and other humans what it was making the machine do. Comments should document the design and the architecture. Not explain the code. A well designed and correct code needs few comments.
No one is a real programmer until they’ve experienced that sensation.
It was more fun before blame, because sometimes it would take 10 minutes to figure out you’re the dumbass.
“Wow, Friday me is an idiot and a jerk.”
deleted by creator
I understand and think the intended content is good. but who would post this with such an obvious layout flaw? it used to be posts with terribly distracting grammar whose intent was relatively easy to decipher. lately it feels like even more basic and obvious rules are being lazily ignored and even shared.
WE LIVE IN A SOCIETY.
My brain honestly just skipped over it until I saw your comment.
I’ll be honest, for a minute I thought it was not a flaw but referring to “Monday Me, on Monday” which is a concept I can relate to
My boss has a morning meeting where we tell him what we’re working on for the day. And every Monday, this meeting is at 8:00 when my shift starts. I’m thankful my name makes me further down the list because I would be stumbling to get that.
He’s a cool guy and not overly micromanager or anything, so it’s not a huge thing, but just reminded me seeing this meme.
Monday morning stand-ups are like, “yeah what AMi working on this week”
“I’ll have it figured out by lunch, probably.”
I’m always pretty happy if I have a bug last thing on a Friday. Gets me right back into it first thing on Monday. It’s kinda weird, but works for me.
If I didn’t do this, I wouldn’t have a job
Gotta leave unfinished tasks and make frivolous jira issues so it looks like there’s a reason to keep paying me to do 2 hours of work a week
Someone forgot a
<br>That is why you should not leave atomic tasks incomplete.
I’d argue that if it’s possible to only partially complete it, it wasn’t an atomic task to begin with.
$ sudo rm -r_…Ok, I’ll type the rest next week
Exactly, each keystroke is an atomic task! Doesn’t that make you feel more productive?
Oh yes, but you know what’s even more productive? We could write an automation script, I can make it type and pause on weekends at 100x the speed!
For someone who gets paid hourly, I’m only willing to go so far with unpaid work past when I’m supposed to stop.
I mean, I do get paid for overtime (flexible work hours) and do like to complete tasks before I go into the weekend, but sometimes all your team mates decide to call it a day, and then yeah, I don’t care that hard either…
I always thought this was just a “me” thing. I’m so glad it’s not. I just wish my wife understood…
//TODO write todo comments in your wip code.
Your IDE will make them easy to find or you’ll just run into them.
I know this is a common joke but how many of us don’t have a problem like this?
Personally I usually have a horible memory but this is never an issue for me, I can stop at any moment and pick up relatively quickly later
Yeah, I’ve developed a habit of writing TODO-comments wherever there’s still something unfinished. And well, I usually leave in a compile error to force me to continue exactly there.
