curious: why would this help?

"...the thin wires carrying power can crack over time, specifically after hundreds or thousands of swivels of the earcups (since they turn 90 degrees to fit flat into their case). That microscopic crack can cause issues with the connection.

By freezing the AirPods, the cold can cause the lining around the wires to contract, temporarily bringing the cracked sections together."

https://www.cnet.com/tech/mobile/airpods-max-freezer-fix/

Sounds ridiculous, but worked on mine! So far, the fix has stuck, too.

Same here, more than a year after the freezer, going strong

The platters come unstuck and can spin again.

I find the consistent anthropomorphization to be grating as well

> If you’ve got the manpower and talent, why not play with it and see if anything makes money. In-house startups with stable capital, all that

We are no longer in a zero-interest rate environment, so I think those experiments are more costly than they were a few years go

You can find the warn notices here. [0] From a quick script I wrote up, it seems that ~60% of layoffs noted on 1/26/2026 are from individual contributors

[0]: https://esd.wa.gov/employer-requirements/layoffs-and-employe...

The new notice came out, that one is for Amazon Fresh only I think. It's 84% ICs now.

Bannon for a while was deeply ingrained in Hollywood. He still earns residuals on episodes of Seinfeld [0], and owns the film rights to Michael Lewis' Liars Poker (even supposedly writing a screenplay for it himself) [1].

[0] https://en.wikipedia.org/wiki/Steve_Bannon#Media_and_investi...

[1] https://www.yahoo.com/entertainment/movies/articles/steve-ba...

He was very close to Epstein. So far as I know, the only mention of Bannon at Turning Point USA was a call to release the 12-15 hours of taped media training he gave Epstein in 2019.

> Claude: they barely have a signin system at all. Multiple account support doesn’t exist. The minimum seat count for business is nonsense. The data retention policies are weak.

Please give me an option for a password (or passkey) or literally anything else that doesn't require either linking with google or going through an email flow for every login

> Connect them with clear APIs that don't have to change all that often, and you can build pretty big things.

Emphasis on clear. It's a challenging endeavor to properly draw and enforce these service boundaries.

Definitely! My metric is "how often do I need to change two systems at once".

This is one of the things monorepos help in some ways (by making it easier to change two systems) and break in some ways (as you now get less annoyed by the split between systems being in the wrong place)

Occasionally I make an analogy to stage acting or opera. In order for the people in the medium priced seats to see the action on the stage, all the actors have to over-emote to make everything that is happening dreadfully obvious.

In a system that is the composition of 30-300 different functional units, nobody will be close to any one part unless they’re the bus number for it. So each piece needs to be dead obvious so you can worry about the consequences of composing them. At the end of the day it’s Kernighan’s Law but rephrased so as not to ignore Conway or Brooks.

In the middle of a billing cycle (which could be a month or year, in some cases), I would agree

name/link?

One would hope that a writer on this subject would have at least a cursory knowledge of statistics