Today we're launching Brief into open beta.
Your AI Product Navigator. The product layer for AI-powered teams.
Built with 100+ teams shipping with agents.
I'm so bored of debates over remote work, 996, open office plans, blah, blah, blah.
these things are all tradeoffs, there's no correct answer, just a lot of signaling that amounts to personal preference for one set of tradeoffs.
over the course of 6 years, I helped 22 teams more than double their engineering velocity.
there's no trick, in fact I wrote how to do it in a blog post I would share with prospects.
more important than ever today, when engineering velocity increasingly means token efficiency.
real quick:
Separate Evaluation and Execution - slow down, consider what you’re doing
Find Yourself - understand your position and what will make you successful
Set Goals - figure out what you need to get done in the next 6–9 months
Categorize - group strategic features by their importance against your goals
Prioritize - stack your strategic features against burning issues and revenue opportunities
Estimate - balance level of effort against priority
Roadmap - communicate themes and map the most critical features to quarters
Execute
Scale
Let It Go!
Put "always use Vitest, never Jest" in the CLAUDE.md. Capitalized it. Agent skims the file, cherry-picks the section it likes, scaffolds the test in Jest anyway. The rule was right there on line 12.
@MatthewBerman /goal refactor until you are happy with the architecture. ensure you live test after each significant step and autoreview/commit. track progress in /tmp/refactor-{projectname}.md
"build me a settings page" is a spec. A bad one. Spec-driven dev just put a name on the thing you were already doing in the prompt box, usually in nine words, usually missing the part that mattered.
@swyx I use it quite a bit, it knows to select the right cheaper models for tasks, but sometimes needs a poke to remember.
I also set up the Workflow > Codex turducken, so Claude knows to route fiddly pedantic work to GPT 5.5.