The last time I saw a news article about this it was talking about how many Airbnb kitchens in SF had been wrecked by teams running field tests for robots doing dishes. Excited to hear about the damage actual plumbing jobs would cause.
Reading up on some of these systems is wild. For example THAAD munitions are wildly expensive, but also a ballistic projectile that physically knocks hypersonic missiles out of the air in flight 200km away. Ultimately $13 million seems reasonable to save a few city blocks in a major city. It just doesn't make sense to use against small arms like disposable drones.
I let them install the free ISP router a year back when they installed fiber in the neighborhood. I assumed I would swap it out the next day, but I haven't had any issues like back in the day. I love shopping for a nice router as much as the next tech nerd, but decent drop-in home networking seems to be pretty commodity now days.
We do a run of 250 similar badges for a non-tech convention every year. ~$10 per badge is about right all in. We've also done runs without ICs (just LEDs, a switch, and button cell battery) for about ~$4 some years.
Agreed that's the best policy for the real contributors, but how do you fight back against the folks using your reviewer's good nature to test their coding agents?
Also, Linus is also comfortable closing 100 PRs as "this looks like garbage". Many communities are softer and try to be more helpful with new contributors.
At Plotly we are dealing with similar issues. We're doing our best to keep up, but it's genuinely hard not to just cut our losses on passer-by community contributions. 3 page issue writeups nobody has proofread, nobody but a bot to follow up with when we try, huge volume of plausible but weak PRs eating up reviewer time. All while we have core work we really want to be focused on rather than merging another bug fix we don't expect anyone but this bot has really run into.
I was ok with the AI writing until I got to the fact that they added Triggers in 2.0 and the article decided that was meh compared to optimizing workers for S3 file access on slow connections. Nope. I'll read the release notes myself.
That's a big jump in the right direction for 6 months. It's certainly more on the level of the light models in terms of cost and performance, but the trajectory is awesome!
Classic case of not listening to the protests. There are tons of examples now of data centers harming communities. The issues range from overwhelming local power grids to literally poisoning the local water supply. The issue is not the data centers, it's that the government isn't enforcing basic rules already in place for these projects. Until the government or the companies demonstrate they'll protect the adjacent communities the protests will continue.
I think the idea is that the latent thinking space in the LLM will be roughly the same for similar quality results - so the majority of executing well could be stripping back and fine tuning an existing LLM.
Our book club has actually noted that more and more mainstream books are written for low attention span. Repeating details ad nauseum and simplifying the plot significantly. So I don't think books are immune to this automatically.
I'm much more concerned about the odds that this tool is vibe coded and will leak the conversations everywhere other than the LLM agent I've already vetted.
There are simple "ORM"s that just map classes to tables and columns to attributes. Basically focused on serialization instead of query generation. I find those to be a good balance.
I suspect most of the critique even back then was around teaching from static written text, not the writing itself. In my experience that aligns well with modern education theory.