Why documentation and comments are cool:

  • 3
    I always leave myself some TODOs with a lot of information
  • 0
    All too relatable...
  • 0
    Oh my god, this is just too relatable
  • 2
    Contrary to this, some of the best advice I was ever given (from a productivity standpoint) was to make sure you leave a task half finished at the end of the day, but spend the last 5 minutes of the day writing notes as to what you're going to do next.

    When you come in the next day / week, there's then no wondering of "where did I get up to", "what shall I work on next", etc. - it's right there in front of you so you can get a move on right away.

    I'm sure it's not everyone's cup of tea, but it definitely helps me - especially first thing in the morning when I'm, ahem, often not the most with it :-)
  • 0
    I use 2 comments in code to know what is the next step:
    //TBD for work that I didn't started to work yet.
    //WIP for incomplete sections, below this line I write a description of what I should do.
    At the begining of the work I search for those comments.
    It's very important to be organized and have a guideline so you will not have dead times trying to remember stupid things.
  • 0
    This is happening to me right now Lmaoooooooo
Your Job Suck?
Get a Better Job
Add Comment