aschla

Doesn't change the fact that most people would rather do those things themselves, but what makes that difficult? The need to work.

The application of robotics shouldn't be in places where human experience is valued, it should be in places where it isn't, like work.

Not fanboying or playing favorite, but I've never come across what you mentioned while using Claude Code. You may indeed be doing something wrong or some part of your config isn't right.

I use Copilot CLI at work, and Claude Code at home, and all harnesses are pretty good these days.

Eh, maybe the geologists did.

I imagine it was what it felt like for miners when they went from working next to each other with pickaxes, to operating massive machines by themselves, although that timeline was much longer and less jarring, taking a generation or two.

"Many cars have an AUTO option now, but would you trust it to choose the right thing? I didn’t, being unsure if it properly accounted for daylight rain driving."

While it doesn't negate the iconography discussion throughout the rest of the article, the AUTO option is the intended default, because it turns on low beams in every case where they're needed, including daylight rain driving, which is based on the use of windshield wipers. I'm always a bit baffled at the modern cars driving around without their lights on. The car does it for you these days.

The ability to select low beams vs daylight running lights (DRLs) is mostly for convenience for one-off odd circumstances where you would want to override AUTO for whatever reason.

The problems with Amazon these days, which may or may not be related to a buyer's specific location:

- Shipping delays. Prime's biggest selling point, is useless if orders aren't shipped in the advertised Prime timeframe. I've quit my Prime subscription multiple times this year because this keeps happening.

- Excessive advertising/sponsored listings. Over half the listings in a search are now sponsored listings, which are often lower quality listings. And Amazon now puts unrelated banner ads next to listings.

- Returns. While returns are typically hassle-free, this leads to abuse of the system. The returns get put back on the "shelf" without much inspection, and there have been more than a few times where I got an item listed as New, which was very clearly Used.

And then there are the cases where someone returns an item, but puts something else in the box for weight, so you end up getting a completely different thing than you ordered.

I once ordered a parallel LiPo battery charging board, and in the box was a LiPo battery, which someone clearly put in the box for weight. That situation was particularly dangerous, because a LiPo, let alone a used LiPo of unknown charge state, cannot be shipped by air and must be shipped by ground. If Amazon had put that box on a plane, that'd be a serious safety issue.

Keith Ledger was a terrible Batman.

Yeah but this one's vibecoded so that means it's better.

A lot of the focus is the effect on pay, but some of the attention should also be spent on competence. There are individuals going through master's degree programs, which are essentially degree mills, to get hired at one of these (or similar) companies, who do not have the basic skills to do the job.

Not everyone, but a significant number, and if you've ever worked with one of these individuals, you know how demoralizing and frustrating it can be. Especially in the typical political climate in a tech company, where saying something even slightly related to immigration will get taken a certain way.

And similarly, Copilot’s Auto mode?

For those of us who do utilize the pre-existing tools and the coding agents effectively, yeah automated code reviews eventually become redundant. But they're still around because there are a lot of devs who don't even glance at what the agents are writing for them. Maybe partly because they don't care to streamline their workflow, or maybe because they've never been particularly good at writing code, and don't actually understand what the agent is giving them.

Lately I've seen some pretty glaringly obvious issues caught during the preliminary automated code review, and the issues seem to be coming from individuals who don't actually understand what the code is doing.

For the rest of us who are actually using the whole stack effectively, the automated code review is essentially a CI gate to protect the repo from the devs who don't know what they're doing.

"If AI inference remains as desirable as Kimball expects, the evolution is likely to follow the same trajectory as the CPU. The CPU didn’t improve along a single axis but instead across simultaneously. Once transistor scaling slowed, chip and system architecture innovations of all kinds proliferated. The list of individual innovations that led to today’s ubiquitous, powerful personal compute could fill dozens of books. A few decades from now, the history of AI inference innovation will show similar depth."

Of the areas mentioned in the article, which are the most likely to have the most prominent innovative impact, and what will they entail?

Kayak fished the St. Croix river last year, on the border of Minnesota and Wisconsin, for smallmouth bass. Crystal clear water. Floated over several huge sturgeon, 4-6 feet long. The way they look, it feels like coming across a dinosaur. Thankfully they're bottom feeders.