Post B6WqpuQAS6DpdTz1yi by lynne@mk.pars.ee
 (DIR) More posts by lynne@mk.pars.ee
 (DIR) Post #B6WqpuQAS6DpdTz1yi by lynne@mk.pars.ee
       0 likes, 0 repeats
       
       I never in my wildest dreams thought code would be the first thing to get automated. I thought copilot was a glorified autocomplete for years. I thought vibe coding last year was a more general but still a yassified autocomplete that required users to do a lot of manual work, doomed to build upon broken incorrect code.But, here we are. I guess the reason why none of us recognize this as cyberpunk or futuristic is that it's just not something most thought possible, until last year, really. And because the densest introspective fog isn't over the past, or the future, but the present.We'll likely end up with a superhuman coder by the end of this year, if it isn't already here, and I think it is, just lacking a harness. At that point, writing code manually will be harmful to a project. Human feedback and taste would stop helping if you can just burn more tokens and let the AI arbitrarily rewrite code if it gets stuck in a local minimum. At that point, maintainers will likely be more of a harm, and reviewing will become impossible.Sure, we can write code for fun. But any public code ends up being more training data. And agents ran by those with nothing better to do will find a way to contact you to nag you about your low-quality code.Human training data will become irrelevant in no more than a year, when synthetic data from majority AI-led projects becomes used in production, at which point anything proven to last a month or two with no bugs is good enough material to use in training.
       
 (DIR) Post #B6WqpufPXQPoOl7Cjo by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @lynnemodern slavery