I've been doing a work-oriented "what I did today" list for ~25 years, and really like it. Originally it started because I needed to bill for my time, but when I went to my current job (over a decade ago) I kept doing it. In my iteration, it is a concise sentence about each thing I've worked on that day. At the end of the month I go back through and review it and write up a "Wins" list.
It's surprisingly useful; I share it with my coworkers and we often consult it if we notice something has been behaving differently starting at a certain date to see what was going on then.
I keep it in a simple text file, running in a tmux on a server, so I have connections to it from my laptop and my desktop. It's currently 19,509 lines.
> It's surprisingly useful; I share it with my coworkers and we often consult it if we notice something has been behaving differently starting at a certain date to see what was going on then.
Not for everything, but things that I do have commit logs for it's a needle in a haystack problem of which repo the commit logs would be in. At work we have ~120 repos, at least a dozen of which I'm likely to have been in over a couple weeks. Other things are likely a ticket rather than a commit (running OS updates, switching to a new haproxy might be a commit from days or weeks earlier when done in staging but the commit log wouldn't show when it was activated in production).
It's very powerful having just a few sentences I can read about what was going on specifically on a given day.
> 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.
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.
I have a spreadsheet where I keep track of excellent work that others do, things that surprised and delighted me, or difficult situations they handled with professionalism. Makes me smile just thinking of it. It will be useful during an upcoming review.
I kind of use my calendar to do this ... if I'm frazzled at the end of the week, it helps to see what I actually did as frazzle brain will have forgotten
that's a nice practice that I do from time to time. Like when my inner self critic starts being too critical ("I'm not doing enough" kind of stuff), or doing things gets harder for some reason, I incorporate the routine of writing done things at the end of the day, and when the situation normalizes I stop doing it. It's usually like a month or two
It kind of sounds like there is a part of you that is abusive and you are rewarding it with this practice, giving it what it wants. I would personally lean in the opposite direction!
What I mean is, you're reinforcing a mechanism of conditional self-approval. A Sisyphean endeavor by definition!
Giving yourself credit for what you've done is fine, but if it comes from a feeling of insufficiency, then at best it's symptom relief that helps you avoid the underlying issue.
I do agree that it's "bad" to need a reason to justify your existence and happiness, but that's totally separate from evaluating your performance at work. I think you're assuming too much.
nah that's actually a practice I learned while being in CBT therapy. I mean, it's not that you reward some bad part of yourself, it's that sometimes you stop noticing all the things you do, like get used to all the stuff and start devaluing it. And by journaling and explicitly stating them you make it clear for yourself that you, in fact, do a lot of things throughout the day. Like "I did nothing today except working and doing house chores, nothing too much, I do it almost everyday" but doing such things and doing it good still requires a lot of effort
I managed to do this for most of the first half of the year, and it was very rewarding indeed. Somehow it sort of dropped off, and something was lost, so I think definitely something to pick up again this coming year.
I think I see where you're coming from but, from personal experience, AI has not much to do with one's interest in learning how to paint or draw. I've picked up drawing again this year not only as a passion but it's something I can create with my own hands. It doesn't matter that AI can do it and can do it much better, it's that I can do it. For fun, for relaxing, for meditating, ...
Multiplying two 100 digit numbers requires the application of a fixed algorithm which can be learned. If you don't know the algorithm it's challenging, if you do it's not.
But that is not true of painting. Painting requires choosing a subject (for its subjective qualities) and then translating what you _want_ to capture about that subject and how you want to represent it in paint on some medium. You will also be applying a theory of mind and perception about the audience of the painting since you probably want it to appeal to them. All of these choices and the skill to combine them into a painting that achieves what you want is vastly more challenging than multiplication.
Multiplication is akin to paint by numbers.
EDIT: it actually strikes me that this conversation gets to the crux of why AI art is so polarizing. It depends whether you view art predominantly as being about the thing that is created or the process of creation.
It's surprisingly useful; I share it with my coworkers and we often consult it if we notice something has been behaving differently starting at a certain date to see what was going on then.
I keep it in a simple text file, running in a tmux on a server, so I have connections to it from my laptop and my desktop. It's currently 19,509 lines.
Don't you have commit logs for this??
It's very powerful having just a few sentences I can read about what was going on specifically on a given 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.
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.
Giving yourself credit for what you've done is fine, but if it comes from a feeling of insufficiency, then at best it's symptom relief that helps you avoid the underlying issue.
Sadly, at this point I would not even call it a challenge, but I would consider it more a pastime.
Sure, but we're talking about a "tada list" here.
Would you write about relaxing and meditation on __your__ tada list?
It’s all a matter of perspective and personal goals, no?
I wouldn't because I would just use libgmp or sympy. And I would certainly not write about it on my "tada list" (if I had one).
Anyway, that's how you should read that comment.
But that is not true of painting. Painting requires choosing a subject (for its subjective qualities) and then translating what you _want_ to capture about that subject and how you want to represent it in paint on some medium. You will also be applying a theory of mind and perception about the audience of the painting since you probably want it to appeal to them. All of these choices and the skill to combine them into a painting that achieves what you want is vastly more challenging than multiplication.
Multiplication is akin to paint by numbers.
EDIT: it actually strikes me that this conversation gets to the crux of why AI art is so polarizing. It depends whether you view art predominantly as being about the thing that is created or the process of creation.