Pinned post
Next time someone asks me what I do for work, I’ll just show them this picture…
@drbarnard
Pinned post
Over the weekend I got my vibe-coding setup pretty dialed in. And at this point I pretty much don’t even type into the text box in Claude Code anymore.View quoted post on X
Instead, I file work via an Artifact and Claude adds them as @linear tasks. Then it builds what I asked for and steps me through checking its work (including its own screenshots from the simulator, but also steps to test on my own). I can leave feedback directly on that page for each issue that needs work.
And then I have a master sheet that tracks all open decision sheets, the ones in process, and the completed ones at the bottom.
I don’t even open Linear at all, just use it as a system of record, somewhere for Claude to document tasks and check them off so that todos and related details don’t disappear from the context window as we keep working.
When we’re at a stopping point, I just ask Claude to work through all the high priority tasks in Linear that have enough detail to start. And for those that don’t, create a new decision sheet outlining what it things it should do and asking for my feedback.
I also use this pattern for generating UI mockups. Claude uses ChatGPT Image (via the Codex CLI) to generate a bunch of mockups of different ways to solve a particular problem. Then it shows me all those mockups on a decision page where I can select one and/or give feedback.
@drbarnard an old SE would be my pick for that. small screen and slow enough to show every janky scroll. do you test on Android too or just iOS?View quoted post on X