amos

neither am I! I've streamed maybe twice in the past 5y, and I have no youtube content planned for 2026 so far. I'm working on a bunch of interesting projects though.

> notepad & pencil approach super valid
I stand by what I said! maybe at some point in my future exists a quieter version of my life, in which I can enjoy doing that.

in this economy???

all of those words ARE in the bible, you're just reading it wrong

notepad & pencil approach super valid too, doesn't quite capture "this div's padding is fucked" without a lot of manual annotation effort

hands are busy petting my cat

new workflow unlocked: recording a screencast then asking claude to:
* transcribe it to English subtitles with whisper-cpp
* use ffmpeg to take JPG snapshots of the interesting moments
* file bugs I've been ranting about out loud
surprisingly effective.

"you could win a $100 gift card!"
or, OR, I could smash my head on a wall, for free!

truly

First Gemini, now Claude. There's not gonna be an AI takeover, they're just not gonna bother

gotta work on your bit flips

[...] Firefox team also reports an astonishing 27% of remaining crashes can be attributed directly to hexes, curses, and other spells.

Q: what do you say when reading debug info entries as memory-mapped C structs instead of decoding them byte-wise?

A: "the DIE has been cast."

I'm new to working on DWARF stuff so I still have jumpscares when reading code and suddenly it screams DIE!* at me.

(DIE = Debug Info Entry)

me: is this good
chatgpt: bro you're overpaying for this SSD by a /lot/
me: yeah, about that...

I didn't. cow'ing my ginormous target/ folder was actually quite expensive. I started building a build system instead x)

> The compromised version was live for eight hours before StepSecurity's automated monitoring flagged it

did they publish /exactly/ at the time of the only oncall person's bed time and did they have a super restful night?

(3/3)

> It flooded the cache with over 10GB of junk data, triggering GitHub's LRU eviction policy and evicting legitimate cache entries

HOW IS THAT EVEN POSSIBLE omg

(2/3)

A GitHub Issue Title Compromised 4,000 Developer Machines A prompt injection in a GitHub issue triggered a chain reaction that ended with 4,000 developers getting OpenClaw installed without consent. The attack composes well-understood vulnerabilities into so...

quick review of grith.ai/blog/clineje...

> The issue title was interpolated directly into Claude's prompt [...] without sanitisation.

bro prompt sanitisation is the wrong boundary, always has been

(1/3)

impressive new github failure mode: having an issue open in chrome made the poor browser peg 1 (one) CPU core. okay.

I'm ready to agree that AI introduces bugs, ESPECIALLY in conjunction with dynamically-typed langs, and also that GitHub's problems have nothing to do with either. Sign me up.

if we really want to point fingers at the things we love to hate I can point out that ruby is an excellent language for poetry but it's absolutely unfit for production software

(and yes I'm—painfully—aware how ubiquitous rails is)

Do you know what they were using before?

friends, it's not the vibe coding. or not "just" or whatever. half the planet is busy vibe coding, github is UNIQUELY unreliable right now. they're doing something different (pejorative)

remember when twitter fired 2/3 of their employees and decided to stop paying their cloud bills

..is this what github also did? is this what's happening? why it's down every. single. day?

q: how do you detect you're running under tool
a: you don't it doesn't set an env var. other than CLICOLOR_FORCE

I refuse to deal with how stupid this is. I quit.

> tool uses a PTY so child processes "can use colors"
> tool takes the raw PTY output, reformats it, spinners turn into a gazillion garbled lines
> look inside tool
> pty.go

🫠

(Oh this is JIT, forgot to say. And no I’m not showing you, it’s not ready!)

achievement unlocked: making a thing that generates executable code that LLDB can step through with full debuginfo so I can see my IR directly in the debugger

in this optimizing compiler pipeline we value clear and honest communication (declaring your clobbers)