- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
I am pretty good at flushing out all memories of my work during weekends these day, so that’s why I have great comments for such things.
(how do I know they are great? I got colleagues thanking me for the helpful comments. How fucking often has that happened to you in your career?)
This just tells me you don’t document well enough.
The code is the documentation.
Anybody that thinks this is always the case deserves a slow, painful and poorly documented death.
Obit: “His life was his obit.”
Legit. Even if documentation can be time-consuming, it is such a lifesaver and makes the whole process of coding much smoother. It means not as much time wasted backtracking. If you think there is any part of your code you won’t understand when you coming back to it, document, document, document.
Sometimes I write some multiline psuedocode comments or/and an explaination of specific choices, especially those invisible choices you make while debugging that aren’t apparent when your just reading through your code.
Good thing to do is make code that is generally readable too lol.
Where’s the Sunday night stress when you realize you’ll have to deal with it all again tomorrow?
I have started to now write all my thoughts down 30 minutes before i go home on friday, will see how it is on monday
I leave post it notes on my computer with keywords so i can remember where I left off. It puts me right back into work mode when I clock in.
