Ryan
@fools-pyrite.com
I don’t think it’s generally accepted but I’ve used “the mermaid problem” after tpsrpg.blogspot.com/2019/11/the-...
The Air-Breathing Mermaid Problem
Every now and then when playing RPGs you stumble upon a mechanic that solves a problem you didn't know you had. This situation is called the...
tpsrpg.blogspot.com
June 29, 2025 at 1:18 PM
I don’t think it’s generally accepted but I’ve used “the mermaid problem” after tpsrpg.blogspot.com/2019/11/the-...
I read the whole series as a kid I think. It was... extremely strange
April 17, 2025 at 1:29 AM
I read the whole series as a kid I think. It was... extremely strange
When I got to work on a dev team that was 50% women, I learned that a lot of the things programmers refuse to do (learn CSS/UX, document code, write tests, etc.) are seen as women's work. which is why dominant programming culture refuses to do them
April 15, 2025 at 12:52 AM
When I got to work on a dev team that was 50% women, I learned that a lot of the things programmers refuse to do (learn CSS/UX, document code, write tests, etc.) are seen as women's work. which is why dominant programming culture refuses to do them
I’m pleasantly surprised that it hurt less this time (my first time was 6 weeks ago). The dermatologist told me the painful part is when the laser does actually heat up a hair follicle enough to destroy it, so as we progress it hurts less
April 9, 2025 at 5:32 PM
I’m pleasantly surprised that it hurt less this time (my first time was 6 weeks ago). The dermatologist told me the painful part is when the laser does actually heat up a hair follicle enough to destroy it, so as we progress it hurts less
The Utena adjacent-beds-but-facing-different-ways shows up in the ED… they knew what they were doing
April 9, 2025 at 5:08 PM
The Utena adjacent-beds-but-facing-different-ways shows up in the ED… they knew what they were doing
What a coincidence, I’m about to pay someone $250 to shoot my face with a laser for 20 minutes
April 9, 2025 at 4:46 PM
What a coincidence, I’m about to pay someone $250 to shoot my face with a laser for 20 minutes
If you’re willing to add a bunch of tooling, there are some pretty good lints in typescript-eslint that enforce “promises may not be returned as void in async functions” and “non-promise expressions may not be awaited.”
Like in React-land I feel like a linter is mandatory for me writing async
Like in React-land I feel like a linter is mandatory for me writing async
April 7, 2025 at 12:02 PM
If you’re willing to add a bunch of tooling, there are some pretty good lints in typescript-eslint that enforce “promises may not be returned as void in async functions” and “non-promise expressions may not be awaited.”
Like in React-land I feel like a linter is mandatory for me writing async
Like in React-land I feel like a linter is mandatory for me writing async
Sorry if I misunderstood, but the orphan rules don't prevent you from having two different versions of a library (Rust supports this pretty well, except for sometimes confusing error messages).
They prevent two unrelated libraries colliding in their attempt to impl a foreign trait on a foreign type
They prevent two unrelated libraries colliding in their attempt to impl a foreign trait on a foreign type
November 22, 2024 at 2:23 PM
Sorry if I misunderstood, but the orphan rules don't prevent you from having two different versions of a library (Rust supports this pretty well, except for sometimes confusing error messages).
They prevent two unrelated libraries colliding in their attempt to impl a foreign trait on a foreign type
They prevent two unrelated libraries colliding in their attempt to impl a foreign trait on a foreign type
Yeah I can't imagine any workflow other than "when we poll the feed, chuck the XML in the parser" and the parser would have to be able to handle RSS 1.0, RSS 2.0, and Atom. It seems like more trouble than it's worth to remember if a feed was Atom or RSS last time you checked
November 2, 2024 at 3:31 AM
Yeah I can't imagine any workflow other than "when we poll the feed, chuck the XML in the parser" and the parser would have to be able to handle RSS 1.0, RSS 2.0, and Atom. It seems like more trouble than it's worth to remember if a feed was Atom or RSS last time you checked
Mildly silly but you could create a dummy Atom feed, load it into a couple readers (Feedly, InoReader, something else) and then convert it to RSS and see how they respond
November 2, 2024 at 3:29 AM
Mildly silly but you could create a dummy Atom feed, load it into a couple readers (Feedly, InoReader, something else) and then convert it to RSS and see how they respond
I think there's a small chance that the feed reader could mark every post as new because it's a new feed structure? But if the posts have unique IDs that stay the same across the feeds, it should be fine...
November 2, 2024 at 3:28 AM
I think there's a small chance that the feed reader could mark every post as new because it's a new feed structure? But if the posts have unique IDs that stay the same across the feeds, it should be fine...