ADHD and hacking an ever growing todo list

Are you familiar with FOMO? Surely.

After using TickTick for long enough and judging my stats, I've noticed I was efficient at solving tasks I focused on, even if I was not always focusing on the most important ones. Yet I have this feeling of being overwhelmed by my self imposed todo list. Whatever I do and it doesn't matter how long I work on my todos, the list keeps growing and distracts me from living my life far from screens. There must be rationale explanations and a solutions, right?

I've revisited my backlog hundred times without allowing me to delete those items nor finding the motivation to tackle enough of them. Occasionally I would do some triage, e.g I bump the priority on some favorite tasks by adding custom tags like "x2", x3" etc. It allow me to find such favorite items later and sort them by priority/urgency.

Yet I still had around 400+ tasks, far from my Inbox Zero principle. How to solve that? I did managed to be efficient at email triage, and at automation, coding, problem solving, I could likely win in any board game, I'm a debrouillard, I know. So how do I solve my tiny issue with my todos without depraving myself of sleep, and without recycling my todo items into the thrash?

The key is most of those todos are not urgent and will be solved in the long term, without specific date. They ressemble more the concept of an idea or an inspiration, or motivation, rather than a problem to be solved.

And that's for now my trick to tackle those needed-for-later items in TickTick -> Tag them as "πŸ’‘ideas" and convert into Note.


redacted.sh: share your logs, not your secrets

Quick post. Sometimes it is necessary to share logs on public issue trackers, forums... and wanting to protect secrets, tokens, IPs is normal.

I've cooked my own minimal bash script for this quest, which I've just added to my public shared snippets : https://gitea.zoemp.be/sansguidon/snippets/raw/branch/main/redacted.sh

#!/usr/bin/env bash

default_rules=(
  's/[0-9]\{1,3\}\(\.[0-9]\{1,3\}\)\{3\}/<REDACTED_IP>/g'
  's/\b[a-zA-Z0-9._-]\+\.[a-zA-Z]\{2,\}\b/<REDACTED_DOMAIN>/g'
  's/\b[A-Za-z0-9+\/=]\{20,\}\b/<REDACTED_TOKEN>/g'
  's/\(password=\)\S\+/\1<REDACTED_PASS>/g'
)

rules=()
while [[ $1 =~ ^s/ ]]; do
  rules+=("$1")
  shift
done
[[ ${#rules[@]} -eq 0 ]] && rules=("${default_rules[@]}")

sed_expr=()
for r in "${rules[@]}"; do
  sed_expr+=( -e "$r" )
done

# If files are passed, process them to stdout.
# If none, read from stdin to stdout.
if [[ $# -gt 0 ]]; then
  sed "${sed_expr[@]}" "$@"
else
  sed "${sed_expr[@]}"
fi

Feel free to reuse, copy, extend, contact me to give feedback! πŸ’š

πŸ’Œ The best way to get in touch is via my email morgan at zoemp dot be. You can also follow me on the Fediverse / Mastodon at @sansguidon@mamot.fr. I speak (a lot) French, English and a bit of Dutch.


Kudos, Hackers

A quick shout-out to everyone who built the web at its best. Using amazing tools, discovering inspiring sites and communities, connecting with peersβ€”no social networkβ€”rocks.

Despite zero promotion, I occasionally get valuable feedback on this blog and my Shaarli. That means a lot, especially during tough times.

We build on the work of brilliant creatives who laid the groundwork. We save time thanks to countless articles, podcasts, tools and platforms crafted by talented people.

For every idea I have, someone smarter and more passionate probably already built something betterβ€”I know that. Yet I keep building, hoping someone will one day build on my work. Maybe I’ll pave the way for others. So, although support is relevant, I prioritize building useful tools and sharing them with everyone.

And to conclude...


Zombiemerge

I do love code reviews but I'm convinced they're best done live β€” reviewed, merged, communicated immediately.

A few weeks ago I did submit changes through merge requests, and a few weeks later I had completely forgot about their implementation.

I context switched a few times since then....

Today the change was merged by the repository maintainers then a few colleagues were discussing one of its consequences. Only because I was in the same workspace, I did react on time.

My mistake was likely to not have communicated more proactively about the change, likely as I'm not the repository maintainer nor the release maintainer so I had no idea when the change would be merged.

Anyway, there are several such merge requests being queued. All recipes for future headaches.


Mastodon