look, i’ve been an artisanal, code-is-craft guy for as long as i can remember. idiomatic, simple, elegant software. it’s been a cornerstone of my professional career. i use vim btw. but make no mistake - ai code will take over the industry. some people may still single origin hand-craft the shit, but it’s akin to a hipster typing poetry on a typewriter.

running clawdbot on an old linux macbook. it’s managing an obsidian vault that’s synced to my laptop with syncthing. planning to see if it provides value for managing side projects and home maintenance. 🦞

gn

using claude code to deal with the backlog of PRs on an OSS project is a live saver. I've been avoiding this shit for 2 years.

every few years I iterate on how I deploy and manage my websites and apps. the latest is a CLI tool called ship.

here's where I'm at with vibe coding - when I'm going from 0 to 1 on a new idea, 100% of the code is generated. I don't eve bother looking at it. I spend most of that time up front writing a spec with ai. half of that is defining the MVP scope, the other half is carefully specify the layers and interfaces of how I want the program structured. I provide specific idioms and coding standards. the result is generally a working advanced prototype, but the code is actually maintainable. the focus on interfaces and components up front is the same approach I've used building production software in the industry. if the interfaces are correct it doesn't matter as much if the implementation is subpar - we can refactor it later. View quoted note →