Initially I kept my ToDo in a text file and I'd just delete things when I did them. Nice clean list of what's remaining, but after a few weeks I felt AWFUL, the list grew faster than it shrank, and it felt like I never made headway.<p>Now I don't delete things. I put a little + at the start of the line for anything I did, a - for anything I decided not to do, and a / for anything I did partially but needs to be revisited. I write a new list each day, carrying-forward items that I feel are worth revisiting.<p>And what's huge is that I can scroll down and see previous lists, years worth, and read all the stuff I did. It's enormous compared to the remaining todos, and apparently that's psychologically important.
For similar psychological reasons I started keeping detailed notes of everything I did at work, at a time when it felt like I wasn't making any progress anywhere. Just seeing a record of when I helped someone else fix a bug, or all the times I moved the ball just by an inch or so - it really makes a difference.<p>If I have 50 pages of things I spent time on, I must actually be doing <i>something</i>!
Not just for psychological reasons!<p>As a scientist, it's best practice to keep a daily notebook called a "lab diary" where you document your work, e.g. details of experiments conducted, day by day.<p>It is sometimes important to prove when you had a particular idea (e.g. for patenting purposes or copyright lawsuits or documenting the history of a field), and it is important to keep track of the details of experiments in order to be able to reproduce them. For that latter aspect, I recommend self-documenting data nowadays, i.e. data that comes with meta-data to explain how it was derived, such as parameters used to create data in an experiment, which I often encode in POSIX filenames (e.g. <method>-n=<n>-iter=<iter>-k=<k>.eval => "randombaseline-n=20-iter=500-k=3.eval").<p>Of course you can maintain such a diary in the form of a plain text file, and I often do that as additional companion, but files are editable, you may lose them, and they have not much worth in terms of serving as a proof;
a paper diary with daily entries, in contrast, is telling a story that is less likely to be fake.<p>It also makes you accountable (in case management asks you what you did on March 3 last year, you'd open your lab diary and could say "that was when we had the meeting where we decided to cancel the XYZ project"), and you can use it to extract achievements for your annual or quarterly performance reviews from it.
I read about how crossing off or checking off todo items gave us dopamine. I adopted that (1998-2000). It worked. I was super productive.<p>I use a similar text prepend now with digital todo lists. It still works, but not quite as much. Perhaps because it's not new anymore.
Also helps you look back a few quarters and see whose goals you’re accomplishing - your own, or the guy next to you who is dishing everything off?
First up, make sure that the Big Ass Textfile is stored in Git (you don’t want your life’s TODO list suddenly vanish).<p>Now that it’s in Git, feel free to delete each DONE task.<p>And finally, have a cron job that on the hour does something like ‘git diff > message.txt; git commit -F message.txt’<p><— this way, you have your day’s TADA list AND your list in now searchable with dates via ‘git log’<p>(This was my TODO list for years until I declared TODO bankruptcy and have gone back to physical cards)
I have the same system, todo become done. I also add done things that I didn’t expect/ plan to do. (Life’s curve ball). I also started tracking “what is the worst thing that happened today”. That’s added perspective that I may think I had a bad day, when in fact I got these things done and the worst thing was actually pretty minimal.
I went the opposite way - my tool aggressively prunes the list when you mark things done. I wanted to improve the signal:noise ratio.<p>I suppose a simpler way to achieve both goals is to alias `todo` to `vim -O ~/.todo ~/.tada` and simply <i>move</i> items from one file to another :-)
Markdown, I use `[ ] - task` and then once it's done I put an X in the []. It works great plus works with subtasks, subsubtasks, etc.
It also means that you have immediate context for your / items when you revisit them.
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.<p>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.<p>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.
I’m praying you have backups. That last paragraph gives me anxiety
Well, I haven't lost them in over a decade... So I have a pretty good track record. The system it's hosted on has had at least one, maybe two hardware failures over that time. A system isn't done being set up until it has backups up and running.
When the server goes up in smoke, you won’t be able to restore from your track record.<p>A simple ‘scp remote local’ once a month will save you from years of “damn… if only I had backed up”
...and tested.<p>I only had to see one machine "that was being backed up" unable to restore from backup. Wasn't mine, but was enough to teach me to test them.
Absolutely! You're preaching to the choir here.<p>However, that said, over ~3 decades I've found that having a successful rsync exit code and alerting when that is not true, along with periodic "full" rsync checksum runs, is effectively a failsafe way of ensuing a good backup.<p>For our less critical systems, this plus "spot checking" by regularly going in and looking at "what did this file look like a few weeks ago" (something we commonly use backups for), has proven pretty effective while also being low work.<p>For critical systems, definitely do test recoveries. Our database server, for example, every week recovers the production database into our staging and dev environments, so backup problems tend to get noticed pretty quickly.
> 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.<p>Don't you have commit logs for this??
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).<p>It's very powerful having just a few sentences I can read about what was going on specifically on a given day.
Commit logs are isolated and per repository. In large organizations, you're usually working with numerous services, often with different owners and split across a number of repositories. Figuring out what caused something to happen can be a fairly complicated process, especially when you don't know exactly where to start digging. Having an overview like this can be invaluable and save you a lot of time.
Commit logs typically only show the coding part, not everything else. It can also be spread out over several repos, or lost if branches are deleted.
> 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.<p>Maybe it makes more sense to have a box per week instead of per day. Or even per month!<p>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 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)
I think weekly or bi-weekly is best since you're aligning yourself with the time scale that most workplaces tend to operate on.<p>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.<p>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 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.
It's a good idea that I might try, though I do like being able to see exactly what I did each day!
> have a box per week<p>Sounds like the weekly report most of my bosses have demanded.
>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.<p>The problem here is that they think it forces you to have an accomplishment. Just write what you did in short form. IT can be "Was very stressed and couldn't get anything substantial done, attended the monthly developer meeting and did some work on documentation".<p>I do this as well to better remember what I have done at work, to quickly be able to document my value towards the company, and to have some "tabs" to show if there are any questions regarding what I did a day.
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 have had many accomplishments, and I've forgotten them all. When it comes to interviewing, I've forgotten most things or can't do easy recall that I can't even speak to them. I have no desire to change though; as long as I made those accomplishments is all that matters, it's kind of like giving gifts - I don't bother remembering what I did for whom.
This is lovely, but in certain life circumstances I've found it more useful to have a to-dont-list, as in: list of things I would really like to do, but shouldn't because there are more pressing matters to attend to and I need to pace myself, otherwise things will turn ugly really quick.<p>Example: day before Christmas eve - the last workday in this region I found myself standing in line to a car wash. There was just one guy ahead of me, but those who were already soaping up their vehicles didn't seem to be in a hurry and it was already 4pm, so sundown over here and I still had other errands run that day.<p>I turned around and the car is currently still dirty, but it'll remain so until I can make time for that, so in 2026.
The list has helped me plan as its forced me to cut things, and just admit I won't have time to do them. For example, I took about fifty books off my shelf and to the little free library. They've been sitting there for years.
Not clear in your example if you have a to-dont list, or just decide "don't" in the moment.
Person that has the ability to have post here in HN is enough of productive at least from most of us reading here. But for us, most of the time staring at the screen reading HN is also nice to keep a list here is what I do:
I have a notebook on my desk that has horizontal lines(what is the word for it) I guess one line is .75 cm wide using that as a day of week I noted what I do that day with codes HackerNews hn, game, read, first job(fj), second job(sj), youtube you, bodybuilding bb, fut for thinking about future life. I keep the list over detail to show you how much a mundane life i have. But be sure more items make you more happy for that day. SO I mean please keep a list of what you are doing taht day
What I want is:<p>A todo list that feeds into a calendar (with a high degree of flexibility) that feeds into a tada list.<p>I’ve been working on this casually for the better part of a year and hope to release something that is home-hostable later in 2026, once I’ve lived with it for a bit.<p>Like I don’t want to remember that I need to do something, I just want a time slot in my calendar that auto populates against a set of constraints, so I can go from moment to moment in a flow. I want to be able to control that todo list and my goals’ time/space constraints with natural language—not some godforsaken form that gives you carpal tunnel. And then I want to see how my progress grows and how much I’m committing to what I want to do.
For similar reasons, I ended up sticking to a bullet journal (ish) format after I tried it ~10 years ago. I don't do long-term planning with it, but I have 1-2 weeks laid out in advance, and years of stuff logged.<p>It keeps a record of things done and lived. In terms of planning and task keeping, the paper format also forces me to let things fall off the list if they won't get done after all.<p>I also joke that I'll be the person who can actually answer if one day an investigator asks me "What were you doing on the night of November 22nd, 2019?"
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
I love the name. I’ve been doing this for a while. My name for it is super boring “todo archive” but I am renaming it next year.<p>Keeping an archive of things I’ve done is great for my mental health. Occasionally, I even look search through it and the associated notes and fish out something useful.
> tada list<p>Ah I thought (and hoped) it was gonna be a list of epiphanies, interesting learnings, new sweetness. You know… taDA!
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 like this idea.<p>I often feel like im better at starting (or just planning) projects then seeing them through, so maybe doing this will force me to finish something.
Lovely paintings!
Love this, I’ll definitely give it a try for a while. I did something similar a while back but on a monthly basis
I did not know about value studies but I have to say, those are gorgeous works of art in and of themselves!
“learned took a CSS course”<p>Extra word there
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
[flagged]
[flagged]
Ragebaiting tsk tsk
You know that the watercolor painting is a gift to his friends and if made with AI it would be undermined to the worthlessness.
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, ...
> For fun, for relaxing, for meditating, ...<p>Sure, but we're talking about a "tada list" here.<p>Would you write about relaxing and meditation on __your__ tada list?
Why not? If one of your goals is to try to relax and/or meditate more, then I feel it’s a valid list entry.<p>It’s all a matter of perspective and personal goals, no?
In today's day and age I definitely would. That's my perspective though and we don't have to have the same expectations from the tada list.<p>"Today I meditated through drawing" is an accomplishment to me worth my personal tada list. Might not be for everyone though, I can understand that.<p>Someone else was making a good point that a daily tada list might be unnecessary pressure and a weekly one feels more balanced.<p>To add more color though, I personally would expect this to compound into an overall tada list similar to OP. At the end of the year I could amount to a lot of drawings and notice improvements over time. But again, AI has nothing to do with it.<p>If we give up on personal accomplishments because "AI can do it" we would go nowhere. But that's my 2c.
How does the existence of AI make watercolor painting less of a challenge for a human?
It obviously doesn't, as otherwise the existence of other humans that are more skilled than you would have the same effect.
Would you call multiplying two 100-decimal numbers a challenge?<p>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).<p>Anyway, that's how you should read that comment.
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.<p>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.<p>Multiplication is akin to paint by numbers.<p>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.
>Would you call multiplying two 100-decimal numbers a challenge?<p>How is this analogous to painting?
Like walking or cycling instead of driving?<p>We should get rid of the 100m sprint in the olympics because a car can do it faster?<p>And anyway, a water color in the original cannot be mistaken for a printed ai picture.
Ai can't do anything like a good water color painting. Also they're physical, like any painting, they look different in real life
Could humanity keep some things for personal enjoyment and enrichment? As a treat?
Why is that impressive?