if smb tells u they review every PR -- probably lying
and the unit tests? written by the same agent that wrote the bug lol
so i built proofrequest:
one agent writes the code, another tries to break it, a judge checks the evidence
shipped & submitted @OpenAIDevs hackathon 🇬🇧
this is the start of the verification layer i'm building for kenno
try it: proofrequest.dev
code: github.com/alterokhq/prq
agents can build bigger features now in nearly one shot
the hard part now is getting the team in the loop
made good progress at forma. excited to show more soon 👀
Replying to @formacity
Tair's building a workspace where product teams and their agents can plan, build and collaborate together.
hyped to be building alongside these ppl <3
3wks in, 3wks to go
come to our final ship & show in london on nov 11th
Over a 1000 founders applied to move to Bristol and lock in with us for 6 weeks.
We chose 16 of the most frighteningly ambitious people, then gave them the keys to our campus, an apartment and $10k each from @solana.
Introducing Residency 002.
one of the best storytellers i have known
that’s what initially pulled me into buildspace
farzas content playbook
There’s a misconception that a successful launch video needs to cost tens of thousands of dollars and feel like a high production commercial. But @FarzaTV has a different approach.
Farza is the founder of @heyclicky and previously built Buildspace, one of the largest online schools for people working on their own ideas. He’s been making videos for over a decade, and today his posts regularly get millions of views. Rather than treating launches as rare, high-stakes moments, he’s made them part of the everyday process of building a company.
Farza sat down with YC’s @aaron_epstein to share his playbook for turning demos into stories people actually want to watch. He breaks down how he scripts videos that still feel off the cuff, why founders should launch constantly, and and how to figure out which channels actually convert.
01:44 — Launch Constantly
03:38 — Start Shipping Demos
05:02 — Show the Process
06:07 — The Clicky Launch
07:43 — Write a Hook That Stops the Scroll
10:30 — Why Farza Scripts Every Video
12:04 — Designing the First 10 Seconds
15:15 — Demo-Driven Development
17:25 — You Have to Take a Thousand Shots
20:48 — Farza’s Formula for Videos That Convert
23:01 — Turning Demos Into Stories
24:53 — Show What You're Actually Building
29:11 — Finding Customers on Social Media
31:02 — Which Platforms Actually Convert?
39:01 — Why Farza’s First Hire Was a Filmmaker
40:49 — The Video Stack
45:41 — The 30-Day Launch Challenge
Tair Asim retweeted
"Product" means working backward from an interface.
The interface -- human, API, CLI -- is where the value happens.
Tair Asim retweeted
Moats! Does anyone have one anymore?
Yes. Yes, they do.
But only a small subset of what people call moats create real long-term value and defensibility.
Not actually a moat:
1. Distribution: This does matter more than ever. Building products has gotten easier, but getting them to customers has not. Distribution, however, does not create durable defensibility. It helps create the raw ingredients for one, but it is not itself a moat.
2. Execution: Yes, speed is critical for startups. But a company that has to sprint forever is not a good business. Ultimately, it will misstep, slow down, and competition will catch up. Speed gives a company more shots on goal as it tries to build a great product and a great business, but it must eventually find something more durable.
3. Brand: The idea is that when everyone is building the same thing, the most resonant brand will win. But for startups, brand works more like customer acquisition spend: Put money in, get growth out. It’s not something that will effectively keep others from competing long-term. Brand can become a true moat over time (as with Coke or Nike or Apple), but it just takes too long to really matter for most startups.
What you're looking for is compounding advantages: a self-reinforcing flywheel that gets stronger and stronger over time, ultimately making a company very hard to compete with long-term.
There are only four compounding advantages that really matter. Every major tech company has at least one:
1. Switching costs: The more deeply embedded a product is in the way a customer works, the harder it is for that customer to switch. This increases retention and revenue per customer, which can be reinvested into the product.
2. Network effects: The more users a product has, the better it gets for everyone. This increases engagement and attracts more users.
3. Scale economies: The more volume a company has, the larger and more efficient its operations can be. This lowers unit costs, funding lower prices or a better product at the same price, further driving up volume.
4. Data effects: The more usage a product has, the more data it generates. This data can be used to improve the product and increase usage.
If you can’t see the potential for any in the startup you’re considering joining, that’s a red flag.
In today’s incredible post, @danhockenmaier shares a simple framework you can run in about an hour after getting an offer:
1. Identify a startup’s compounding advantage
2. Gauge how strong it could get
3. Measure whether it’s working
Inside: dozens of real company examples, the specific metrics to track, and benchmarks for what good and great look like.
Read it here: lennysnewsletter.com/p/how-t…
moving off git and eventually github will be a thing soon
prs are already dying. they were built for human collab, not agents
improve upfront verification + agreement on what to build
then replace vcs with smth built for agent-first envs
then gh actions infra slowly gets out of the way too
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
do you read ur PRs?
one prompt now ships what a sprint used to
nobody can review that
i think plans are the new PRs
so i'm building kenno -- a multiplayer workspace for teams building with agents
if ur team ships with claude or codex, dm me
i'd love to demo how kenno can help you
testing out a new idea for teams + agents
@formacity creative juices flowing





















