The Three Files That Made Codex /goal Reliable Enough to Walk Away From
The Hard Part Was Walking Away The first time I ran a codex goal command on something that mattered, I sat there for twenty-eight minutes pretending to check email while...
Every week, I share the exact techniques that actually work—not the theory, not the hype, just the stuff I've tested until my keyboard begged for mercy.
No spam. 1–2 emails a week. Unsubscribe anytime.
You're three hours into a Claude Code session. The feature works. The tests pass. All that's left is the picture at the top — a featured image, a hero illustration,…
Read Full IssueThe Hard Part Was Walking Away The first time I ran a codex goal command on something that mattered, I sat there for twenty-eight minutes pretending to check email while...
The first time I used Codex /goal, I sat at my desk for twenty-eight minutes pretending to do other work while an autologin plugin built itself from a one-paragraph spec....
How I Used 8 Codex /goal Runs to Build a Browser Game From Scratch ended with a line I’d been sitting on for the whole post: “Part 2 is where...
One paragraph describing a game idea. Eight /goal commands. Seventy-eight minutes of autonomous Codex time. A playable vertical shooter in the browser. The WordPress plugin post was one goal, 28...
Those pro-level workflows that make you wonder why you ever did it the hard way. Hidden features, unexpected tricks, 'wait—it can do THAT?' moments.
Not theoretical 'imagine you had a user...' scenarios. Actual implementations from actual work. Copy, paste, adapt, ship.
That tedious stuff you keep putting off? Automate it. That repetitive task eating your afternoons? Gone. More time for the work that actually matters.
Join developers who've stopped fighting their tools—and started building with them. One email. Once a week. Genuinely useful.
No spam. Unsubscribe anytime. Seriously.