sebiwi

Tech, fun, and cookies

Latest writing

Re-counting the florbs: churn ultimatum Aug 25 2026

Counting the florbs: BRIN indexes, rollup tables, and a 90-second query Jun 22 2026

On Operations, DevOps and soft skills Jan 17 2019

Software Craftsmanship and OPS scripting: a love story Aug 16 2018

Ansible Container: Chronicle of a death foretold Jun 19 2018

Recent comics

You'd think they'd stop trying after the great success of their blockchain currency, or their augmented reality dumpster fire. But naming their agent after a source of inspiration? If I wanted my agent conversation history to be used for political advertisement, I'd give it to Cambridge Analytica myself. So I guess it inspires me to vomit.

Muse

And faded on the sides, and long on top. Alright, design complete. Would you like me to proceed with it? Yes, and auto-accept edits. Yes, and manually approve edits. Keep planning. ...What.

Haircut $I had to do it again. How come you keep finding yourself in these situations? Server management just finds me. What was it this time? I just needed to know what was running on port 17002. Something like "lsof -i :17002"? Get-NetTCPConnection -State Listen -LocalPort 17002 | Select-Object LocalAddress, LocalPort, @{N='Process';E={(Get-Process -Id $_.OwningProcess).ProcessName}}. Can't you just use brainfuck instead?$ The Powershell diaries: part 2

Hmm, that does not seem to be working. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Let me just retry. Incident history: the retry storm was fixed by pulling the plug on our AI assistant. Hah, sorry!

Retry Storm