I consider LLMs basically high-frequency StackExchange trading. You gotta be exact and not keep the thread alive too long or driftrot is real though. Much faster to parse, though.

Also, the ones that can access the web are great for “I want specific lib x version y to solve a weird problem, what support libs are needed?”

I just realized how odd it would be to see people walking around in brandless clothes. As odd as when someone removes all the badges from their car.

The advertising has been so prevalent for so long that it has been normalized. Fascinating.

They’re about 2% better at being a telephone IVR than the older ones, probably at 6x the power cost.

I had an AI render a simple diagram for a presentation with explicit instructions. It rendered a Rube Goldberg nonsense graphic. I included it anyway for the lulz. Sure, they will get better, and maybe some day be almost as useful as the Enterprise computer. No way they’ll be Lt. Cmdr. Data this century.

People in the past have used the entertainment bus to get into the flight telemetry data, hopefully only in a read-only state, but that will only be true if you trust the competence of the IT group that set up the programming for the switches.

Just be careful of where you try to write data and you should be fine! (and stay away from /dev/wing0 and /dev/wing1 on the network mount!)

They run Linux now.

Don’t forget BetaMax, MiniDisc, ATRAC, LDAC (which I’m sure is just ATRAC over Bluetooth 😂 ) - amazed they won BluRay, honestly. They also won the 3.5" floppy format, which the kids only know as “the save icon”.

Is Docker caching some file you need instead of the changes applying? Raaaage!

But! My context!!!

Truthfully, it’s amazing how often the next morning, with a fresh brain, it becomes an easy fix.

Reverse-compression!

Season 1 still feels great. 2 gets a bit weird and feels more like a B show. 3 is like shark-jumping, but seeing a timeline jump that shows the now-very-near future is good for some “whoa” moments like, “this is what the continents will look like with sea rise,” but probably feels more like having to work your way through season 1 of TNG.

Didn’t mind spending exercise time watching all three though.

He also apparently watched a lot of SeaQuest DSV, and is trying to make it a reality. Hyperloop: SeaQuest. Electric cars: SeaQuest. Big car dashboard screens: SeaQuest. Magic Space Science: SeaQuest. CyberTruck…Apple Mouse ADB gen 1-ish wrapped in aluminum foil. I guess what I find most fascinating is that I have similar mental maladies to him, but I learned instead of just being perpetually dumb. It is actually disappointing that he chose to not learn and just ride the walrus instead. No idea why anyone worships him.

It sucks when you have a leak sensor, estimate the likeliest place that water will appear, miss it by a few inches thanks to the way water goes where it wants, and you end up having to manually catch the leak.

https://www.thewindowsclub.com/how-to-disable-windows-thumbs-db-files-from-being-created this kills that.

.Trash-999 was already taken by a metal band.

Metadata that’s a holdover from the 1980s MacOS behavior. Hilariously, today, NTFS supports that metadata better than Apple’s own filesystems of today. They can hide it in Alternate Data Streams.

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

Helps a bit.

It helps to be a little bit stubborn, but mostly, remind yourself it’s just software at the end of the day too. So many devs are judgy and think there is only one “good” way to solve a problem, which ends up creating a sort of tunnel vision. As soon as you let that go and just know that every problem could have any solution, especially the unexpected, you see your way through faster.

It doesn’t matter if the way it was working is “right” or not, it was working, for reasons, so fixing it, is just teasing out those reasons. Be it from humans that may still be around, but most of the time, by feeling the code out.

I even see the struggle externally from afar when companies I used to work at release a new feature that touches very legacy code and, time and again, the new feature is buggy AF. The new dev likely had no idea what the old dev was thinking or why, and thusly, breakage. Neither of them is right or wrong, the solution from the past likely was obscure due to constraints that no longer exist, the new solution can be done easier due to a plethora of libraries that now exist, and getting newEasy to jive with oldBespoke trips the new dev up as they unravel what looks like pure chaos.

Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.

It’s rare to see a newborn meme. Soon it will be pixelified to all the doom.