3 ms·
For me, it’s not that the actual coding is faster. It’s that you can do other things at the same time. If I’m writing an integration, I can be researching the
by SkyPuncher 1y ago
For me, it’s not that the actual coding is faster. It’s that you can do other things at the same time.
If I’m writing an integration, I can be researching the docs while the agent is coding something up. Worst case, I throw all of the agents work away while now having done research. Best case, it gets a good enough implementation that I can run with.
- weatherlite 1y ago> Worst case, I throw all of the agents work away while now having done research The worst case is you take the agent's work without really understanding it, continue doing it indefinitely and at some point get a buggy repo you have no idea how to handle - at the exact same moment some critical issue pops up and your agent has no clue how to help you anymore.
- krageon 1y agoI don't think GP said they couldn't do their job, but you instantly jumped to incompetence. That seems little uncharitable to me.
- weatherlite 1y agoHave no idea what GP can or cannot do and wasn't talking about that. I'm saying what the worst case that can happen when people work with agents, and it can happen to anyone who isn't carefully verifying and testing the agent's work.
- m_fayer 1y agoTotally. I feel like it’s akin to jamming with someone. We both go down our own paths for a bit, then I have a next step for it, and I can review what it last came up with and iterate while it does more of its own thing. Rinse, repeat. This is more fun and less energy consuming than “do it all yourself”, which certainly means a lot. This way works for me. Any time I tried to treat it as a colleague that I can just assign tasks to, it’s failed miserably.