Thread

1. jrm4 · 1785957320 · focus · HN ↗

   Relatedly, there needs to be some kind of way to distinguish between types of LLM usage. Nothing more boring -- and often not even favorable or useful to a semi-hobbyist -- than just one-shotting something with Claude;

   Vs. what I do. I've always done tons of little quirky automation type things with bash -- that do actually strongly become a part of my life.

   Today? Yes, that -- but more and faster. I'm actually typing out way less code, but getting more of what I'd like done, and which couldn't be done without some bash (and now python*) knowledge.

   Before AI, knew something about python but never typed e.g. more than 20 lines of it myself. I now am able to use it extensively regardless because, like with lots of languages, reading is easier than writing.

   1. slaymaker1907 · 1786022779 · focus · HN ↗

      You're right, there are tons of different workflows you can do. One of the more innocent ones, regardless of you opinions on vibe coding, is just using the LLM to understand the code base better. Even if I'm vibe coding something, I will often start by having the LLM construct documentation for the current code flows. It's a document that is useful to me as a human because it mostly just gives me code pointers and tells me what it does as part of the larger whole. It's useful for the LLM since it saves a ton on time and tokens in the long run.

Unofficial Hacker News client; not affiliated with Y Combinator.