3 ms·

> Maybe the most obvious con: a tada list forces you to have an accomplishment each day so you can write it down, and this added stress to my day. Maybe it mak

by andai 11mo ago

> Maybe the most obvious con: a tada list forces you to have an accomplishment each day so you can write it down, and this added stress to my day. Maybe it makes more sense to have a box per week instead of per day. Or even per month! At least in my own life I've noticed that focusing on daily output tends to be demoralizing, whereas if I look back over the months I am often amazed by what has come out of me.

sublinear 11mo ago
I think weekly or bi-weekly is best since you're aligning yourself with the time scale that most workplaces tend to operate on. I've actually had good conversations with nervous junior devs to help them see the value of their contributions this way. There's a lot less reason to stress out if you're working steadily and see that things are going according to plan. I know devs can be focused on the literal tasks at hand, but the "10k ft view" is not just a cheesy thing people say and it should not be ignored. It gives perspective.
ardeaver 11mo ago
I can also imagine that you might need to change your definition of what an accomplishment is. I tend to think of it as something that has a measurable output, but difficult-to-measure progress towards an outcome is also something (despite what product managers might think)
- ferngodfather 11mo ago
  > change your definition of what an accomplishment + Get out of bed before sundown
  - metabagel 11mo ago
    + Spend a day above ground
IshKebab 11mo ago
> have a box per week Sounds like the weekly report most of my bosses have demanded.
- fastasucan 11mo ago
  Thats where it started for me. Writing a couple of sentences per day meant the weekly report was easy.
egonschiele 11mo ago
It's a good idea that I might try, though I do like being able to see exactly what I did each day!
nicbou 11mo ago
I would stick to a daily note because you lose a lot of granularity after a week. With journaling at least, I rarely remember how I felt even 24 hours ago.

by andai 11mo ago

sublinear 11mo ago

I think weekly or bi-weekly is best since you're aligning yourself with the time scale that most workplaces tend to operate on. I've actually had good conversations with nervous junior devs to help them see the value of their contributions this way. There's a lot less reason to stress out if you're working steadily and see that things are going according to plan. I know devs can be focused on the literal tasks at hand, but the "10k ft view" is not just a cheesy thing people say and it should not be ignored. It gives perspective.

ardeaver 11mo ago

I can also imagine that you might need to change your definition of what an accomplishment is. I tend to think of it as something that has a measurable output, but difficult-to-measure progress towards an outcome is also something (despite what product managers might think)

ferngodfather 11mo ago
> change your definition of what an accomplishment + Get out of bed before sundown
- metabagel 11mo ago
  + Spend a day above ground

IshKebab 11mo ago

> have a box per week Sounds like the weekly report most of my bosses have demanded.

fastasucan 11mo ago
Thats where it started for me. Writing a couple of sentences per day meant the weekly report was easy.

egonschiele 11mo ago

It's a good idea that I might try, though I do like being able to see exactly what I did each day!

nicbou 11mo ago

I would stick to a daily note because you lose a lot of granularity after a week. With journaling at least, I rarely remember how I felt even 24 hours ago.