Don’t ask it to make changes off the bat, then - ask it to make a plan. Then inspect the plan, change it if necessary, and go from there.

> some people really are saying "fix this" instead of saying "x fn is doing y when someone makes a request to it. Please attempt to fix x and validate it by accessing the endpoint after and writing tests"

This works about 85% of the time IME, in Claude Code. My normal workflow on most bugs is to just say “fix this” and paste the logs. The key is that I do it in plan mode, then thoroughly inspect and refine the plan before allowing it to proceed.

> complain they aren't getting great results without a lot of hand holding

This is what I don’t understand - why would I “complain” about “hand holding”? Why would I just create a Claude skill or analogue that tells the agent to conform to my preferences?

I’ve done this many times, and haven’t run into any major issues.

I get what you’re saying, but this is important enough that it doesn’t feel like nitpicking:

You’re not going to learn anything from history if you only read it in one direction.

It's also for parents who want to give their kids a "real computer" without breaking the bank.

My 12-year-old wanted a laptop to build mods for games. I got her a new M1 Macbook 8GB - $425 from Walmart, refurbished.

My 17-year-old wanted a laptop for college, but wasn't sure what she needed or wanted yet. I gave her my 2020 M1 MBP.

If either of those situations arose today, I'd get them a Neo.

I went through a two-year period where I didn't have a decent job and couldn't afford a computer of any kind for myself. I ended up spending some time volunteering for a local non-profit, and they gave me an "old laptop" they had in storage. This was in ~2005.

It was a Sony Vaio, and the only thing I really remember about the hardware/specs is that it had a physical scroll widget under the touchpad on the edge of the case. Software-wise, it was running some relatively locked down version of Windows. I installed Arch on it and used it to rebuild and manage the non-profit's website.

The other thing that I remember from it is that it was my entrance into using the terminal as my primary interface - the first place I used Vim regularly, and the first time I'd installed tmux. One day I was trying to test a dropdown or something on their website, and discovered that my touchpad didn't work. It turned out to have been broken by an Arch update, which wasn't terribly surprising. What was surprising is that once I'd traced down the issue and corrected it, I realized that it had been broken for almost two weeks. I'd used that computer every day and hadn't needed to use a mouse even once.

> realized that it had been broken for almost two weeks. I'd used that computer every day and hadn't needed to use a mouse even once.

I had a similar experience on a smaller scale a few weeks ago. I keep an extra keyboard of my preferred model (Pinky4) in a backpack to take on the go with me, but I only have one pointing device I really like (Ploopy Classic Trackball), so I pack up my one and only as needed. I'd gotten home, started using my computer, and an hour or two passed before I reached for the trackball and noticed it wasn't there. It was still in my backpack. I've got Sway keybinds to jump between my most-used programs instantly, and use a lot of terminal stuff as well. I can definitely imagine if I were on a low-end machine I'd go even longer without noticing.

I'm a man in my 40s. My eldest daughter is 17. We have the same first name (spelled differently, at least) and have had many cases where medical records have gotten confused.

We always double-check dosages for medications before taking them.

Wait until you live in the same zip code with another person that has the same first name, last name and date of birth!

This was a story I found amusing when I read it: "Letter from Chicago. Confusion oriented medical records."

https://pmc.ncbi.nlm.nih.gov/articles/PMC1605484/

When I was 18 I got called up for jury duty along with someone with the same name and age. It was confusing. They started referring to us by the suburb we lived in. Luckily both of us got passed over.

Interesting you should say that, as not a single one of the Iranian emigrants that I know would agree with you.

Extrapolating the politics of people who stayed based on the politics of people who chose to leave is not going to get you very far.

I’m aware of selection bias; I’m basing my view on their perception of family and friends “back home”.

Iranians who left and live in the west want Iran to be the west. Nothing changed.. they all held those beliefs before the war.

In their current implementation, yeah, they’re pretty bad.

There is a need for something like it, though. A sow will absolutely lay down on her piglets and suffocate them.

> A sow will absolutely lay down on her piglets and suffocate them.

This makes me really curious because that behavior seems very maladaptive for a species. That leads me to wonder if something else, ie. the environment or domestication, is leading to this behavior rather than pigs being really, really prone to wiping out their own species. Does anyone know why they do this in a farm environment?

Pigs are adapted to singular survival. A stressed sow will often eat the piglets. And that stress can be being a mother for the first time.

There are a lot of environmental factors, like snuggling for warmth being unsafe.

But by and large... Pigs give birth in numbers. They can afford for half to die, and still proliferate. They don't need to be 'good parents'.

Pigs breed like rabbits so their evolutionary path hasn't been to ensure individuals survive at the highest possible rate, their path was to have a dozen babies at a time so that even if 80% of them get killed or eaten, their population still grows and thrives. For a farmer losing 20% of their pigs because the mother sat on babies and suffocated them is a massive loss of money, for a wild pig it doesn't matter as much because 3x more will get eaten by predators and there is already another dozen on the way within a week or two of giving birth to the first litter.

Some of the loss likely is due to keeping them penned up, however there are also losses for not keeping them penned up and letting baby pigs run among a herd of many adult pigs, some of which will attempt to kill piglets, especially females who have not had piglets yet. Pigs can be absolute viscous as hell and will readily eat other living animals if they think they can get away with it, including other pigs, and some mother pigs have been known to cannibalize their young even under ideal situations. Pig farmers have themselves been killed by pigs from passing out or getting knocked out in pig pens and the pigs seeing them as a free meal not to be wasted.

They definitely do it in the wild as well, though likely at lower rates.

They reproduce very quickly - evolution is a numbers game, and yield isn’t part of the equation.

We're also genetically engineered them to be much heavier than they would be naturally.

That depends on the breed, but sure. I’ve not seen it happen at noticeably lower rates for less sturdy breeds for whatever it’s worth.

Both things you mentioned.

This isn’t a red/blue issue.

Flock is no more populate on the right than it is on the Left.