Mostly a writer these days. I work in technical marketing @Vercel.
Joined March 2008
- Tweets4.8K
- Following127
- Followers1.2K
- Likes443
Pinned Tweet
No matter the process, you can tell when someone isn’t doing the work.
But it isn’t as simple as “AI slop or not.” There’s a spectrum of fully generated to assisted to “artisanal, homemade sentences.” If it’s generated and untouched, you notice quickly. Assisted pieces usually feel incongruent if the author phones it in on edits.
There are some interesting ideas around evals for writing, which is highly subjective, but I have no idea how we could create universally applicable benchmarks (current tools probably pattern match and use synthetic examples).
"Go through this session (including pre-compaction) and print your response to every prompt where I corrected you, pushed back on your output, or replaced your draft with my own rewrite."
In my last job I moved into product because I love working with engineers. They possess a unique combination of creativity and clarity.
Working with @lgrammel on this piece was a true joy. It's an incredible system, built with an incredible amount of thought and care.
We built a software factory for AI SDK.
Each step is an agent, and humans merge changes. Four weeks in:
▪️ The factory authors up to 35% of merged PRs
▪️ It closed 70% of issues in July
▪️ Open bugs are down 25%
vercel.com/blog/building-a-s…
I run a content agent in a local harness, and if you don't pay attention to how your terminal client handles shell sessions, things can get wonky fast.
Coding harnesses are great at sorting things out when you back everything with git, but I agree worktrees are a great way keep project workflows isolated.
day 9 of overthinking your agentic engineering setup
unless you want to be a solo vibecoder forever, learn to use worktrees to create distinct lanes for your agents to work within
before I start any new feature work, I setup a new worktree (your agent can do this itself too). nothing else changes
I never experience agents stepping on each other's work or mixing PRs that are ready to ship with work that's still in progress
Not too long ago I thought to myself, "It seems crazy that there isn't a cross-harness plugin spec." Just a few weeks later I was tapped in to work on the Agent Plugins launch with @hefnerdotpro.
This was a fun one, and a great picture of what it's like to work @vercel: shortly after you feel friction, product ships to remove it.
Introducing Agent Plugins, an open standard for extending agents.
Supports Agent Skills and MCP, with more to come.
Built in collaboration with: @awsdevelopers, @code, @cursor_ai, @github, and @openaidevs.
vercel.com/blog/introducing-…
Justin is a talented writer. Every talented writer I work with who uses AI as part of their process:
1. Understands its power and
2. Is constantly frustrated and underwhelmed by it
AI for code can feel like magic, but you can't write tests for a great blog post in the same way you can for a feature. More importantly, in writing, words are the final product, where code is a means to a product end, and that's one of the reasons writers feel these sharp edges more acutely.
AI is capable of some wildly complex tasks, but I often find myself most delighted in the simple things it can do, like cleaning up my desktop.
"The most important skill in prompting is expertise in the domain you’re prompting for."
@sjgoedecke is right, and this is why even though many perceive AI as "good at writing," it doesn't make people good writers. seangoedecke.com/llms-reward…