Comment by strangescript

Comment by strangescript a day ago

7 replies

Everyone is still thinking about this problem the wrong way. If you are still running one agent, on one project at a time, yes, its not going to be all that helpful if you are already a fast, solid coder.

Run three, run five. Prompt with voice annotation. Run them when normally you need a cognitive break. Run them while you watch netflix on another screen. Have them do TDD. Use an orchestrator. So many more options.

I feel like another problem is deep down most developers hate debugging other people's code and thats effectively what this is at times. It doesn't matter if your Associate ran off and saved you 50k lines of typing, you would still rather do it yourself than debug the code.

I would give you grave warnings, telling you the time is nigh, adapt or die, etc, but it doesn't matter. Eventually these agents will be good enough that the results will surpass you even in simple one task at a time mode.

kibibu a day ago

I have never seen people work harder to dismantle their own industry than software engineers are right now.

  • marssaxman 20 hours ago

    We've been automating ourselves out of our jobs as long as we've had them; somehow, despite it all, we never run out of work to do.

    • kibibu 15 hours ago

      We've automated bullshit tedium work, like building and deploying, but this is the first time in my memory that people are actively trying to automate all the fun parts away.

      Closest parallel I can think of is the code-generation-from-UML era, but that explicitly kept the design decisions on the human side, and never really took over the world.

  • strangescript 21 hours ago

    What exactly is the alternative? Wish it away? Developers have been automating away jobs for decades, its seems hypocritical to complain about it now.

sponnath 21 hours ago

Can you actually demonstrate this workflow producing good software?

hooverd a day ago

Sounds like a way to blast your focus into a thousand pieces