4 ms·

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,

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 4mo ago
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 4mo ago
  >All of it. Even this?
  - konovalov-nk 4mo ago
    Well, don't automate your thinking ;) If you can do this then yes we'll transition to AGI/ASI. But thinking (and understanding) is still largely human.
- hashmap 4mo ago
  [dead]
deadbabe 4mo ago
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.
- konovalov-nk 3mo ago
  GUI is just sequence of events (mouseclicks, scrolls, keypresses) on top of semantic tree (if we can call div class soup as "semantics"). But we can record it since long time ago and simply compress/remove noise. TUI is better since it usually operates on keyboard, it's good for visualizing 1d/2d data (which is most of GUIs btw). CLI is least interactive of them all I'd say and it limits what you can do. Either you have a solved problem that you can trigger with a button push, or you have to input tons of flags to configure behavior, or write a config file and re-use it. To me this seems sub-optimal. I'd rather use voice activation + NLP to let LLM figure out what I want to do, present me with a quick "are you sure? + exact CLI command" and then I can press it. Forgive me for lengthy text, I was just thinking outloud whether my assumptions about TUI/CLI make sense. Do you agree?
ValentineC 4mo ago
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/ https://xkcd.com/1205/

konovalov-nk 4mo ago

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 4mo ago
>All of it. Even this?
- konovalov-nk 4mo ago
  Well, don't automate your thinking ;) If you can do this then yes we'll transition to AGI/ASI. But thinking (and understanding) is still largely human.
hashmap 4mo ago
[dead]

deadbabe 4mo ago

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.

konovalov-nk 3mo ago
GUI is just sequence of events (mouseclicks, scrolls, keypresses) on top of semantic tree (if we can call div class soup as "semantics"). But we can record it since long time ago and simply compress/remove noise. TUI is better since it usually operates on keyboard, it's good for visualizing 1d/2d data (which is most of GUIs btw). CLI is least interactive of them all I'd say and it limits what you can do. Either you have a solved problem that you can trigger with a button push, or you have to input tons of flags to configure behavior, or write a config file and re-use it. To me this seems sub-optimal. I'd rather use voice activation + NLP to let LLM figure out what I want to do, present me with a quick "are you sure? + exact CLI command" and then I can press it. Forgive me for lengthy text, I was just thinking outloud whether my assumptions about TUI/CLI make sense. Do you agree?

ValentineC 4mo ago

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/ https://xkcd.com/1205/