Approximately half of the people with schizophrenia don’t believe they are ill, which is why they refuse treatment (see: anosognosia). It is a very strange illness.

Depending who you believe, approximately half of them are unable to see they are ill (re: anosognosia).

I suspect this is the case with many mental health conditions / neurodiverse conditions; after all, people grow up with them and if their environment is not affected or making observations (e.g. people are told or convinced that what their brains do or tell them is abnormal), why would they doubt themselves?

But this is a narrow path to walk, because if you see something and someone tries to convince you it's not there, who is right?

This is why some mental health conditions are pretty terrifying, because doubting your own mind is terrifying.

It’s more complicated than that, re: anosognosia.

Re: anosognosia.

Maybe for some people. For me, they work perfectly and integrate with all my other Apple stuff (MBP, iphone, TV, iPad), everything just works. My stress levels demand it.

Indeed, like MagSafe charging—they simplify. Simplicity has a premium.

That said, my first pair failed out of Apple Care and resulted in a full cost replacement. The APM sub is littered with stories of the BT module failing.

I’m sure it is ludicrous to some but I often measure value by utility and I go through entire workdays wearing this product.

I moved to a beach town and found out the tides app only exists on my Apple Watch. I went through 10 iOS apps that didn’t work properly or wanted me to pay subscription before giving up. I just don’t understand… do they not use their own products or something?

I recall being shocked the first time I used Azure and realizing so many resources aren’t namespaced to account level. Bizarre to me this wasn’t a v1 concern.

And the naming restrictions and maximum name lengths are all over the place: https://learn.microsoft.com/en-us/azure/azure-resource-manag...

Storage accounts are one of the worst offenders here. I would really like to know what kind of internal shenanigans are going on there that prevent dashes to be used within storage account names.

I wonder if it's related to the fact that Windows as such weird rules about allowed file names. Like not directly obviously, more like culturally inside microsoft.

I’m pretty sure Azure was built out with Hyper-V, which was built into the Windows kernel. So everything that relied on virtualization would’ve had bizarre case insensitivity and naming rules.

I’ve lost track of servers in Azure because the name suddenly changed to all uppercase ave their search is case sensitive but whatever back-end isn’t.

Isn't case insensitivity a Win32 thing only? I would not expect it to impact stuff in Hyper-V or the windows kernel. AFAIK for example NTFS is case-sensitive.

NTFS supports case-sensitivity, but if you have case-sensitive distinctions in a directory that's marked case-insensitive, bad things happen. (Those bad things are probably entirely deterministic, theoretically-predictable, and documented in one of Raymond Chen's big books of Windows sadness, but that doesn't mean I want to deal with them as a mere mortal.)

I would not dismiss something like that directly being the cause. Not the reason you can't name a file "CON" on Windows, but it's very likely some weird ass thing they were stringing together with Windows Server and Hyper-V and SMB backed them into the corner we're all in now

> It exists only for the people who think it exists

Right. Which means it does exist. And the point of the article is to bring about self awareness of the phenomenon so that people can improve.

I think you have the same goal with your comment, but your style of communication needs work.

Ironically, I would argue you might benefit from caring a little about how others perceive you.

That telephone cord is impressive.

Pretty standard option for any home with a teenager, to be honest. Long enough to drag the handset into the nearest coat closet when needed.

Mom’s listening along on the other phone with her hand covering the receiver.

We have them at work on our voip phones so we can roll around to each other's cubes while talking to a client without putting that client on speaker. We have headsets and the like too but you're not always wearing it when the phone decides to ring.

You discarded the context within which he made that statement.

i read this

> If you have a job like that, or work at a company like that, the sooner you quit the better your outcome will be.

AI will render your job to be rent seeking. Like self driving cars will automate away truck drivers - do you not think they need to be laid off because of AI?

> Like self driving cars will automate away truck drivers - do you not think they need to be laid off because of AI?

geohot is talking about AI has its limitation and that it won't truly replace the human yet. Truck drivers and some people who contribute net positive value are not rent seekers at the moment.

AI could render our jobs to be rent seeking, we don't know when.

We have unions actively opposing self driving cars mainly to protect their own jobs. In fact I think it’s much more common for a company to lay off because of real ai impact than anything else