maybe don't delete the item?
Ask HN: How do you not keep track of what you did yesterday (and this morning)?
21–30 of 37 posts
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#22what is blocking you? where are you trying to go? why?
This is what matters.
what u did isn't that interesting anymore. too late to revert. just history.
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#23i used to have this problem; it was due to me not doing a good enough job keeping a paper trail of what I was doing in tickets/git/my journal and having lots of stuff going on.
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#24I have a slack reminder to write down what I did before I get off each day. Works great!
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#25I'm having a hard time imagining a stand-up where everyone on the team does not already know what you were doing yesterday. The board has your closed tasks and your current task. Your stand-up is to give progress on your task. What's going on that people don't know what task they have been working on?
Because I wake up 5 minutes before this meeting and my mental energy is spend on making coffee.
>> What's going on that people don't know what task they have been working on?
> Because I wake up 5 minutes before this meeting and my mental energy is spend on making coffee.
Funny.
I was asking about the format of the dailies, though. "How did the 'endpoint creation' task go, yesterday, KptMarchewa? Did you complete it?" is a question even a coffee-deprived sleep-addled dev can mumble an answer to.
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#26I write everything down in my personal wiki, everything, absolutely everything, emails, chats, work I did, tasks. If it ain't written down I didn't do it or know it. Works like a charm for recalling what I did and also lends some perspective.
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#27I use the app Things and each day have a todo / note called "standup 2022-02-24".
I make a very quick note of each major thing I do, each thing that blocked me and things I know I need to do tomorrow, e.g:
- Y: created basic CI pipeline for application
- B: was blocked from working by having pointless meetings in the afternoon
- T: add security scanning to CI pipeline
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#28I use Qbserve [1] after seeing it mentioned in a previous thread.
Really helpful for seeing where time was spent over the course of the day/week. Collected data all stored locally too
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#29I use Qbserve [1] after seeing it mentioned in a previous thread. Really helpful for seeing where time was spent over the course of the day/week. Collected data all stored locally too [1] https://qotoqot.com/qbserve/
Cool. I’ve not come across this before. I currently use the app “Timing” [0] on Mac which is similar (and pretty good).
The downside with both of these though is no local sync across multiple Macs, which is a killer feature for my use case. Timing offers sync but it’s cloud-based (no E2E) which rules out using it for me. For now I just have separate sets of tracking data on a couple of Macs…
I may give Qbserve a closer look though.
Re: Ask HN: How do you not keep track of what you did yesterday (and this morning)?
#30Earlier quoted context omitted.
Because I wake up 5 minutes before this meeting and my mental energy is spend on making coffee.
>> What's going on that people don't know what task they have been working on? > Because I wake up 5 minutes before this meeting and my mental energy is spend on making coffee. Funny. I was asking about the format of the dailies, though. "How did the 'endpoint creation' task go, yesterday, KptMarchewa? Did you complete it?" is a question even a coffee-deprived sleep-addled dev can mumble an answer to.
I wouldn't put it past myself to forget an endpoint I implemented yesterday, that's why I document them as soon as I finish.