AndreasPK

Makes me wonder what's worse. The bias of the average curator or the bias of typical training data.

It's the next step after teenagers calling you sir.

I think it's some overflow in the USB driver on the printers side. It works fine for a day or so. But eventually USB on the printer just stops working until I reset it's power.

"But why the power cable?"

The printer actually doesn't have any way to reboot it without cutting it's power ...

The year is 2026.

I can buy a toner subscription for my printer.

I have to reset my printers power cable before I can print over USB.

#Priorities

Red line is Python. Forgot to make sure the legend is also on there 😅

I found myself debugging a Perl script today.

And I realized Perl basically isn't a thing anymore. It used to be inescapable when I started to get into "computers".

Probably involves a Ritual at that point.

Unironically my banking apps changelog.

Kinda surprising the hashes add much. But makes sense given llms don't really carry state like a normal program would.

2026 will be the year of sound just working on Linux. We all just have to believe.

Inject those security vulnerabilities straight into my veins.

The european Superbowl experience.

Go to bed. Wake up. Realize the superbowl was yesterday.

I'm so compiler brained I keep typing llvm when I mean llm.

I think the uptick there right at the end is the start of #AmeriHac! But this is me speculating wildly.

The 2nd big spike right after was when one of the main runners died.

I think the big spike after the 17th was additional CI runs for releases that were in the works at the time.

I love being unable to edit my posts.

Picture unrelated

CI Wait times for GHC Gitlab over the last month.

Poor Americans. Hours are in GMT.

Also no guarantee for correctness of underlying data. This

I think it's often an acknowledgement of responsibility which might or might not come with strings attached. But I never viewed it as carrying "a favor" forward into the future inherently.

Also does that make "Sorry, but that's not my problem" a paradox.

The server had a hickup towards the end. But I got most of the data.

I've let this script run for hours and all I got was this lousy exception.

Watching this python script run for over 5 hours so far, and starting to wonder if I'm going about this all wrong.

Didn't take you for a Rust developer.

At least round up to a even 30.

Day 4(ish) of Rust: Most of my problems are now of my own design. Turns out the hard part about programming is still the programming.

Weaponized FOMO.

I was booking a flight and seems you now can pay to lock in a price without actually buying a ticket yet if you are afraid of missing out on the current cheap price.

Depends. Did you tell it to role play as a Sailor in 1600 first, which means the concept of copyright hasn't been invented yet?

Fomo sapiens intensifies.

Makes me trust their security design about as much as receiving the old password in plain text when I request a password reset.

The current security model of Agents seems to be the equivalent of "just don't open any untrusted mail attachments".

For example I seem the have the choice of allowing it to edit any files in my project. Or ask for permission on *every* edit.
Without a way to whitelist files/sub folders. Wild.