after i had enough context to start making connections, I couldn’t put it down

dell’s xps hardware quality can also be dubious, multiple people I know (including myself) have had issues in years past with high end XPS machines. If they’re trying to meet a low price point and can’t cut costs on the enclosure it’ll be interesting to see how the reliability of the internals fares

I’m much more able to navigate without the map than I was before I started this experiment - and it’s had the added benefit of giving me the ability to know what part of the 101 I’m on solely by the angle and shape of the nearest exit.

I hope eventually AI gets to a point where I can split the difference between ambiguous and incidental friction like this, although tbh I’m not really sure what that would look like.

if bitwarden is acquired and the new owner decides an open source version of their product is not a business necessity, without someone actively supporting the salaries of engineers it’s unlikely to continue to be secure for much longer.

> “We didn’t tell people what to use because there’s a really big continuum of how people use and how they respond to that dosage,” Brooks-Russell said, explaining that they wanted these studies to reflect how people use cannabis outside of the lab.

Actually a really smart process decision - in past studies I’ve seen they always used a prescribed dose but having the participants choose makes a lot of sense

I originally learned about it through [the trueanon podcast](https://www.patreon.com/posts/episode-477-kold-135145076), their episode on it is really good.

> Connecticut’s Insurance Department recently reviewed EviCore and Carelon. It found no problems with Carelon. EviCore was fined $16,000 this year for more than 77 violations found in a review of 196 files.

$16k is such a low fine that it’d be funny if it wasn’t so sad. fines should be increased to actually represent a threat to the company - maybe as a % of yearly profit?

our system is so fucked dude

https://kubuntu.org/news/kubuntu-26-04-release-notes/

my favorite that I have set up is a tag in my bathroom that shows me today’s weather and chance of rain when im brushing my teeth - I haven’t been caught by surprise in the rain since :)

it’s not an actual limitation on the harness.

cognitive debt is a real problem in my domain (embedded software) because AI simply can’t debug the symptom when the reasons for the bug aren’t in code, and a stack trace may not exist. finding the REALLY hard bugs requires in depth systems understanding and the ability to connect things you’ve seen around the codebase together - and the fix usually isn’t adding code, which means the patchwork fixes Claude likes to do only makes things worse.

that said, it’s made writing harnesses and supporting tools WAY easier and faster, and my workflow is better for it. Searching the git history for the why of things is also made way easier; helping me to reason more effectively

For determining the number of balls, i had an idea but not sure of how well it’d fit in. Could you feed the listing title, unit count, and description into an LLM with a basic “figure out how many balls are in this listing and make sure that number makes sense with the price” prefix prompt and then store that number with the ASIN? One LLM call per product should be pretty low cost, and it could automate a bunch of repetitive manual work