[konovalov-nk]

Lemme give you more signal than this how to automate yourself.

1. Write down everything you do in text. Don't skip any details: thoughts, why, how, who, what, and so on

2. Add details. More details. Even more details.

3. You will see some patterns. This is algorithm.

4. Extract algorithms into specs/intent graph. But for god's sake don't use markdown as final substrate. At least write BDD/Gherkin.

5. "Sufficiently structured problem becomes the solution"

You're welcome.

[konovalov-nk]

Once I did all of that for what I'm doing (I'm just a web dev...), it turned into a rabbit hole so deep I am now questioning reality itself

I'm not kidding though.

I had a mental breakdown multiple times throughout 2 months while I was "writing down in minuscule detail what I'm doing".

I debugged my brain and realized I have OCD (in addition to ADHD) and it made me so happy that I'm now free from this terrible mistake of not making any mistakes at all.

And I never felt so productive in my entire life.

Incredible things will just start happening once you start writing your thoughts.

It doesn't even matter what you are writing. Just write it all down.

All of it.

[latentsea]

>All of it.

Even this?

[ValentineC]

Haven't seen xkcds being shared in a while, but here's the obligatory xkcd for whether it's worth the time (even prompting takes time):

https://xkcd.com/1205/

[deadbabe]

If you live in the terminal and do everything via CLIs, it becomes even more obvious what steps you need to automate this stuff.

Unfortunately, a lot of developers are terrified of the CLI for some reason and cling to GUIs and TUIs.