Cli on ferkakta.dev

I answered 114 AWS Well-Architected Review questions from my terminal

Fri, 03 Apr 2026 23:00:00 -0500

I was fourteen questions into the AWS Well-Architected Review when my wrists told me to stop. Each question is a page: read the description, check the boxes, type notes into a 2084-character text field, click Next. The Container Build Lens alone has 28 questions. I had two more lenses queued — the main Well-Architected Framework (57 questions) and the Generative AI Lens (29). That’s 114 questions total, and the console wants me to click through every one.

I was wrong about shell completions for 15 years

Wed, 01 Apr 2026 15:00:00 -0500

I thought shell completions were tab-operated Jinja — fill in the blank, template-style. Type half a filename, press tab, get the rest. That’s all I thought they did.

And the AWS CLI completer kept confirming that impression in the worst way. When you’re typing aws s3 cp somefile.txt s3://bucket/, the completer hijacks tab on the local path argument and sits there forever trying to guess AWS-side completions that will never come. You’re done with the AWS part of the command. You just want to tab-complete a filename. It won’t let you. AWS hogs the empty space where your possibilities want to go, because it thinks it’s important to block your progress in case you wanted to speak to any of its 867 pet names. As John Roderick and Merlin Mann put it on Roderick on the Line: keep moving and get out of the way.

Do not fake smallness

Fri, 27 Mar 2026 15:00:00 -0500

I found an old gist from my BAM consulting days. It shows csvq — a one-line alias that turns any CSV stream into a queryable in-memory SQLite database with JSON output:

alias csvq="sqlite3 :memory: -cmd '.mode csv' -cmd '.import /dev/stdin s3' '.mode json'"

Pipe a CSV into it, write SQL, get JSON. I wrote it for a colleague I was initiating into my ways. The gist is polite. It shows the output being piped into jq '.[]', which is perfectly respectable Unix.

Recovering Claude Code sessions from history.jsonl after index corruption

Tue, 10 Mar 2026 09:00:00 -0600

I still have every email I’ve sent and received since 1998. I don’t lose data. So when Claude Code stopped resuming sessions for a project I’d used daily for months, I didn’t think “oh well.” I thought “where did it go.”

The project directory still existed in ~/.claude/projects/. There was even a sessions-index.json in it. But the actual per-session JSONL files — the ones that contain the conversation data — were gone. Every one of them. The index was a catalog pointing at empty shelves.