What I think is also good about the piece is that it shows how using this tech eventually funnels people down a particular direction. This is captured also by this exchange on lobste.rs: https://lobst...
@nprofile1q... I read that thread and was very surprised by Simon's recommendation to let it rip, and review changes in larger chunks. I see the rationale, but I don't see how that can do anything but increase the possibility for mistakes. Of course, additional guardrails should be in place. At what point does the energy investment in guardrails obviate the initial benefit? I'm not sure.
But I'll also add that one big reason I didn't just let it make changes autonomously is because I wanted to understand the model's process. The journey was the point. What I read in that thread was so output-focused that it missed the point entirely.
But I'll also add that one big reason I didn't just let it make changes autonomously is because I wanted to understand the model's process. The journey was the point. What I read in that thread was so output-focused that it missed the point entirely.
1