Chris Harrington @ironiridis@mspsocial.net

Weird wobbly power late this evening. Thought I was imagining it.

Much to my disappointment, I am teaching both of my children Python.

Also: I do not know any Python.

This is on *every* power cycle, including S4 hibernation. It's frustrating enough that I don't trust my laptop OEM for another purchase in the future, but I know they don't care because I'm small potatoes. Consumers hardly buy computers anymore. It just kills me that these flaws are baked into the hardware, since I'm not just going to create more e-waste due to inconveniences.

When it does die, though: @system76 or Framework, for sure.

To my annoyance, this firmware has multiple bugs in fact. One bug is where the LCD panel enters a "dynamic contrast" mode, which adjusts brightness(??) based on screen content. This is awful, so I turn it off. But enter the third bug: on power-up, the display does not honor the setting in the firmware, enabling the dynamic contrast thing anyway. To fix this, you must turn the feature on, then back off in the firmware settings.

You'd think that "performance" would cause the fans to spin up and the temperature to rise, but in exchange you get maximum processor output. Instead, what appears to happen is that the fans throttle down on this setting; they'll still kick in, but only well past the thermal throttling of the CPU. Consequently, the "performance" mode is actually really similar to the "quiet" mode... it does not really go faster.

The firmware on my laptop has four thermal settings: default, cool, quiet, performance. This is the classic Triangle-shaped Optimization problem; the vertexes of the triangle are "go fast", "stay cool", and "stay quiet". Default optimizes right in the middle. Cool optimizes for the "cool" vertex, sacrificing "go fast" and "stay quiet". Quiet, too, does what's on the tin. Remarkably, though, "performance" does not behave like I'd expect.

I don't really want to make the computers go today.

A lot of our culture is influenced by popular media, like TV shows. And TV shows have an incentive to modify their content to make it easier to consume. (eg Two characters that are familiar and alone together explicitly using eachother's name to introduce them to new audience members.) I wonder if we unintentionally adopt any of this behavior.

Okay, YouTube Music, I'm going to need you to understand that during hyperfocus "repeat 1" should not ever be overridden. This track needs to repeat, preferably louder, for the next hour. Thanks!

Anyway, leave it to Amazon to write 2003-era #java in #golang

you basically NEED to use this leather-bound buckle-fastened Necronomicon of a condition builder to produce the syntax because there's like 250 reserved case insensitive words that are an absolute minefield with no way to safely quote or escape attribute names except to list them all explicitly before your query like you're reimplementing zlib or something.

Seriously the WithFilter and WithCondition methods both take ConditionBuilder constructions and there's no context in which you can use both a Filter and a Condition (the former is for Queries, the latter is for Updates, but who cares: they express the same idea) but this SDK apes the type system by collapsing both into a Condition thing that then has methods to extract the weird bend-over-backwards string renderings of these directives, and you could just use the string syntax directly BUT

Sometimes, the struggle for understanding ends with a moment of clarity and satisfaction. Recently, though, it feels like the struggle usually ends with a series of expletives and "why do we even HAVE a distinction between Condition and Filter here, who is fucking using BOTH OF THESE at the SAME TIME it's NOBODY THATS WHO ffalsiNAUENU"

Probably should have CW'ed with "computers -- sorry"

Thursday: Okay, gotta write that job executor today! *writes conditional scheduling logic*
Friday: Alright, gotta write that job executor today! *writes enqueue/dequeue logic*
Today: Ugh, gotta write that job executor today. *writes mid-truncating output capture buffer logic*

The incomprehensible urge to take apart expensive appliances and put Raspberry Pi's in them

"Myoclonic Jerk? That was in an episode of House, right? Please god just let me sleep"