Steeph's Web Site

Go To Navigation
Show/Hide Navigation

Entries tagged 'cat:ADHD'

Today I've learned slow progress is still progress.

I haven't only learned that today. But I'm starting a "Today I've learned…" series of entries, in which I won't be picky about actually having learned something that day for the first time.

I've learned that tiny steps towards a goal may only seem tiny compared to the size of the steps you were or are imagining taking. The are always infinitely larger than no step at all. If you think you should be able to do/finish a task today, you may not. But if you try and only finish it by 50%, you've done what was possible and learned that this task can take longer than you thought. That's two good things. If you image you can do 10% of a task today, but you end up only finishing 1% of it, that's not as tiny of a progress than it may feel. It is only small in comparison of what you imagined before starting. If the task doesn't go as well as imagined, including not as fast, it runs the risk of getting put of because it's no fun, frustrating or doesn't seem worth the effort. That is not making progress. Doing 0.1% of a task today is progress. And still infinitely more progress than planning to do it tomorrow or next week.

There are probably sayings about this "wisdom". It can seem banal. But sometimes it can be very relevant ro be reminded of this fact. Doing the next step is the way to start to do something. If the next step is not clear, thinking or inquiring about the next step is the next step. If it's complicated/many unclear steps are involved, written and drawn plan can help. The next step is the single one thing that you have to do. All the complicated stuff comes after. If that is taking a tool out of a box, that's it. Then you can still think about the next step. If a task seems overwhelming or you're acting as if it does, do just one or two things, then see what comes next. Or do it for only one minute even though you know it'll take fifty times as long. Once you've started, you'll probably do it for more than a minute. If not: Fine, that was the plan. That was still progress.

It is easy to forget about this perspectve. There are ways of reminding oneself of them. But this entry is not about them. Although I didn't intend to go the entry in that direction, I'm going ahead and add an ADHD tag to this to make it clear that I noticed in what direction it went.

The frontmost part of my tongue it littered with forgotten thoughts and blog entry ideas.

I wanted to post about three things today after work, when I'm back with my computer. I will likely remember one or two of those things when I'm back at work and can't take a break to write a blog entry.

Just Try It! It Will Have Been Simple Afterwards.

Again and again I encounter technical problems (software bugs, hardware defects) that seem to be nearly impossible to fix without having had a proper education in the respective field. The simple, and correct, way to getting rid of these types of problems surely is to declare them not a problem. Buy a new device, convince yourself that you don't want the feature anyway, make somebody else solve your problem and blame them if it isn't perfect or breaks again.

But in those cases where I do find the motivation to try and repair something myself, it is often easier than expected and always so in hindsight. If you have repaired something yourself before that you initially considered to be a problem that is above your capabilities, I congratulate you on this eminently gratifying feeling that more often than not seems to come with this experience. If you haven't, this sentence doesn't address you.