When I stumble upon an unsolved or undocumented problem and solve it, I like to document it here.
I recently revisited a CDK project I published in late 2022 — cdk-private-rds-with-lambda — and ended up rewriting most of it. The original worked fine, but it carried complexity that didn't earn its keep: projen for project management, an EC2 bastion host for database access, password-based auth via Secrets Manager,
I needed a plugin that could run a multi-phase workflow autonomously — start a task, wait for it to finish, check the result, start the next one. I built it in Claude Code using Stop and SubagentStop hooks, then rebuilt it in OpenCode using session.idle events. Both work. The orchestration
OpenCode plugins have three extension points: tools, skills, and commands. They're discovered differently, and two of the three work automatically from an npm package. Commands don't. This post documents how I set up a bunx setup script to handle the gap. How OpenCode discovers plugin artifacts
The feature-workflow plugin tracks features in files (docs/features/[id]/plan.md), but that state isn't visible without reading the files. Multiple terminal tabs running Claude Code have no indication of which feature each is working on. The statusline integration solves this by writing the current feature ID
A single LLM call rarely produces perfect results. Ask an AI to organize a movie library into collections and you'll get inconsistent output—sometimes creative, sometimes missing obvious franchises, sometimes grouping unrelated films under vague themes. The solution isn't a better prompt. It's a
Organizing a large media library into meaningful collections is harder than it sounds. With 1000+ movies, you need something smarter than keyword matching. "Star Wars: A New Hope" and "Star Wars: The Empire Strikes Back" share a franchise, but a text search for "Star Wars&
With proper workflows and setup, Claude Code has been amazing for me to get a project 80% complete. Where I have struggled (not just with Claude Code, but in general) is to complete a project. I think I did fairly well with this project: https://github.com/schuettc/plex-collection-creator with
The other day I noticed a post on BlueSky: hailey (@hailey.at)in other news i replaced ohmyzsh today with starship. its quite nice out of the box, though god knows why both the AWS and gcloud plugins are enabled by default lolBluesky Socialhailey I have used ohmyzsh for a
Authentication typically happens in one of two places: the frontend checks if a user is logged in before showing protected UI, and the backend validates tokens before processing requests. There's a third option—verifying JWTs at the edge, in a Cloudflare Worker, before requests reach your backend infrastructure.
API keys for backend authentication create a fundamental challenge in web applications: the credentials need to authenticate requests but cannot be exposed to clients. Hardcoding keys in frontend bundles or environment variables leaves them visible in browser developer tools. Anyone who opens the network tab can extract the key and