Thread

1. Arubis · 1789753677 · focus · HN ↗

   Yes, and: the most important time to use your brain isn't in the loop.

   That _is_ valuable, and will remain so, but the temptation to turn it off is there because the loop is good and getting better at what it does. Once you're in the loop, with the rare high-value exception of catching total mistakes nad redirecting, you're mostly choosing between similar-yet-reasonable options. This isn't so much right-vs-wrong as relativistic optimization. Letting the loop do the work will get you a mediocre result quickly, and that's usually fine.

   The most important time to use your brain is _before the prompt_. Once you engage with your LLM and agent, you start biasing yourself, and its reasonable suggestions constrain your visibility into other options, other worlds.

   First, use your brain. Then write the prompt.

   1. xendo · 1789754390 · focus · HN ↗

      I don't agree. I'm recently a huge believer in Programming as Theory Building. The software creation itself is the part that makes you understand what you are building. It's impossible to understand things before you start building them, initial prompt can help you explore, but the idea that after that you can lean back is ridiculous. Most or maybe even all successful software projects are still heavily relying on the best software engineers. That's why anthropic and others are still hiring SDEs.

      1. CamperBob2 · 1789754481 · focus · HN ↗

         That's great, but you and your family will go hungry as a result. If not this year, next year.

         Your stance isn't new, if it's any comfort. I heard (and probably said) exactly the same thing when C compilers started getting good enough to eliminate the need for most assembly coding.

         1. xendo · 1789755056 · focus · HN ↗

            I will take my chances. Software is part of my identity and I won't abandon it that quickly.

            1. CamperBob2 · 1789835100 · focus · HN ↗

               Mine, too. Now I can create a lot more software, just as I did when assemblers gave way to compilers.

               The idea that this is a bad thing is just bizarre. In technology, what's anomalous isn't change, but things staying the same for 50 years, the way they have in the software business. K&R circa 1972, if transported forward in time, would instantly recognize my workflow today as being essentially the same as theirs. That's what's fucked up. It's good that something genuinely new and interesting is happening at last.

Unofficial Hacker News client; not affiliated with Y Combinator.