5 ms·

I've been doing it only for 3 or 4 years, and this 100% lines up with my experience. There are times when I haven't been consistent, and it always comes down to

by soiler 4y ago

I've been doing it only for 3 or 4 years, and this 100% lines up with my experience. There are times when I haven't been consistent, and it always comes down to feeling that "I can't do a good job of it right now, maybe later..." and then I miss that day, and miss that week, etc. I use the mobile app Pixels for journaling though. It lets the user define custom tags (I track emotions, activities, wake up time, body pains...), which for me is pretty useful, but I would say it also raises the floor on the effort it takes to make an entry, because I don't like to miss data points on those tags. So to the reader: start small, be forgiving, and don't worry about getting good data. 99% of the value of journaling is the practice.

Random_Person 4y ago
I'm glad you pointed out the tags issue. I've been using Daylio for a while now because I like doing little entries throughout my day and I initially set up a bunch of tags. Lately those tags have started to feel like a burden because I worry about missing an entry related to those tags. That burden hasn't become significant yet, but it is something that's bothering me and I could see it be an excuse later on to just give up on the whole thing... i.e. the data junky in me says what's the point of tracking data if the dataset isn't accurate.
- bbor 4y ago
  I’ve been working on the same thing. Does anyone here have tips on how to filter/mask a given time-based data set so that it infers data where possible (i.e. if I logged one mood for the day, it’s probably safe to map that across the whole day) and ignore unrealistic data (I.e. if I logged one meal for the day, that’s probably not a useful day of data). So far just been winging it on a case-by-case basis but curious if there’s a fundamental pattern I’m missing
ravishi 4y ago
My current solution is to write many times a day (each hour when possible). Write short sentences with key information and then move on. Sometimes I'll edit some old entries to remove details and reduce length. The best part is that "key information" also changes, so it also ends up reflecting what was important to me at the time.
- tony_codes 4y ago
  Interesting, haven't heard this approach before.

by soiler 4y ago

Random_Person 4y ago

I'm glad you pointed out the tags issue. I've been using Daylio for a while now because I like doing little entries throughout my day and I initially set up a bunch of tags. Lately those tags have started to feel like a burden because I worry about missing an entry related to those tags. That burden hasn't become significant yet, but it is something that's bothering me and I could see it be an excuse later on to just give up on the whole thing... i.e. the data junky in me says what's the point of tracking data if the dataset isn't accurate.

bbor 4y ago
I’ve been working on the same thing. Does anyone here have tips on how to filter/mask a given time-based data set so that it infers data where possible (i.e. if I logged one mood for the day, it’s probably safe to map that across the whole day) and ignore unrealistic data (I.e. if I logged one meal for the day, that’s probably not a useful day of data). So far just been winging it on a case-by-case basis but curious if there’s a fundamental pattern I’m missing

ravishi 4y ago

My current solution is to write many times a day (each hour when possible). Write short sentences with key information and then move on. Sometimes I'll edit some old entries to remove details and reduce length. The best part is that "key information" also changes, so it also ends up reflecting what was important to me at the time.

tony_codes 4y ago
Interesting, haven't heard this approach before.