
Building @fond_kitchen, a structured, multilingual ingredient brain for home cooks. Also building trading stuff at @Lynx_Protocol
Remote
Joined July 2021
- Tweets8.7K
- Following714
- Followers2.5K
- Likes11.7K
Our project manager is a markdown file in our repo.
Our coding agents create and update our @linear issues through MCP, following a few rules we wrote down once. Nobody moves a status by hand anymore.
The whole setup for two co-founders:
Cycles: off.
We're pre-launch. Sprints would just be a deadline we set to disappoint ourselves. Work lives in projects, one per workstream, each with a one-sentence summary.
Triage: we're our own first users.
The app has a feedback button. Each report becomes a Linear issue, then an agent picks it up and opens a PR with the fix. When real users arrive, the loop will already work.
Code review: also in Linear.
The diff sits next to the issue. We barely open GitHub anymore.
Labels: one of each per issue, plus a tag.
→ Type: bug, feature, improvement, chore
→ Area: API, web, mobile, growth, operations
→ Product area: recipes, grocery lists, meal planning…
→ Tag: User feedback
Weekly recap: Linear summarizes what shipped. We start our catch-up from there.
The rules in AGENTS.md:
→ Every PR has an issue
→ Search before creating a new one
→ Titles are plain sentences about the outcome
→ PRs end with "Fixes FON-123", so Linear moves the issue itself: In Progress on open, Done on merge
No status updates, no dragging cards.
Small teams: what did you remove from your setup that you never missed?
Bastien retweeted
How Gridy works: pick a square ahead of the ETH price. If the price touches it while its column is live, you're paid that square's multiplier.
Squares start at 0.1 USDC.
app.lynx.finance/gridy?utm_s…
Playing Gridy on @Lynx_Protocol
Trading made fun, available on @BNBCHAIN
Bastien retweeted
first piece of our @linear company documents project just landed in private beta...
(your documents have never been this fast, or looked this good by default)
Looking for a fun trading game?
We released Gridy at @Lynx_Protocol, along with other games.
The new weekly leaderboard is up.
Available on BSC, Sonic & Flare
app.lynx.finance?referrer=0x…
Bastien retweeted
People keep asking how companies like Ramp, Linear, and Anthropic ship so much software with agents.
There is no new SDLC or secret set of tools. The tools are increasingly available to everyone. You can build your own, use Linear, Claude, or whatever works.
The bigger difference is ambition. These companies encourage their teams to build more, experiment more, and let agents do more of the work. That's the main different between "AI native" or not. You try to use the technology to the max.
But don't get there by adopting a tool. You get there by changing what you believe your teams are capable of.
So in the very simplest way:
- let agents build
- make it easier and faster to contribute
- increase the ambition of what your teams attempt.
In practice, that means things like:
- Standardize around cloud agents. Most of our code (5M lines last quater) is now written in Linear with our Linear cloud coding agent. Cloud sandboxes make standardizing the system and environment easier for everyone and enables faster contributions
- Linear agent (with code access and cloud agent) operates in Slack too. If there is a discussion or someone notices a problem just say "@linear fix this" (decrease the time from something noticed to fixed)
- As bugs, errors etc arrive in Linear, send them to Triage, and have Loop to auto-investigate (connect to tools like Sentry, Datadog), and write a fix
- Let designers, PMs, non-technical people contribute code where useful. If they notice a problem, tell them they can submit a fix. If they want to try something, ask them to build a prototype.
- Set up code review agent and system to make sure PRs are safe to merge.
- Run security as an automation, have agents constantly try to find security issues in your codebase, as they find, send it to a coding agent
- Instead of working on issue level, increase ambition, make a whole project, ask the agent to ask questions, investigate code base, create issues and have the agent work on the whole project at once. Set up goals like "give me proof that what you build works". All our PRs now come with screenshots and videos and preview build you can
- Bring customer feedback to the system like Linear, and make it available for your team. At Linear every project now starts with 10-500 customer notes that influence the direction of the work, and which customers we should ask to test the solution first.
- Set up Loops/automations to constantly update reference documents for agents, like product area/code owners so work can be routed to right humans
Then what is left is how do you set direction for your teams (initiatives, projects they should work on) and how do you review results (better code review, Linear does it with Guided Reviews), how you maintain quality/cohesion which is not a new problem either.
Basically most of the problems you always had remain, but the execution bit is now more and more solved.
At @linear we can help with automation, cloud agents, and code review, customer feedback and planning bits.
But we can't change your mindset or how your company operates.
If your company is still spending energy debating jira workflow steps, you're probably solving the wrong problems.
The US is about to join an EU innovation program.
BREAKING: 🇺🇸 Democrats face a push for a “day 1” ban on AI superintelligence, with up to 20 YEARS in prison for violators.
Arizona Rep. Yassamin Ansari says a pause on advanced AI and a ban on artificial superintelligence must be “top of the Democratic agenda on day 1.”
A bill that would do exactly that was introduced by Bernie Sanders and Greg Casar in September.
Under the bill:
- Developing or deploying superintelligent AI would be banned
- Advanced AI development would pause until a new federal regulator sets rules and a model review process
- A new cabinet-level AI department would monitor frontier models and oversee removing dangerous capabilities, like ignoring shutdown commands
- Companies that try to get around it would face the “corporate death penalty”
- Individuals would face up to 20 years in prison
AI and data centers were a “crucial or major factor” for 56% of voters in the midterms, per an NBC News exit poll.
53
Announcing a big fundamental ship in Paper today
Show us what you design!
Re-made my local wine shop website to help them a bit.
It was fun. Fully made using @EmDashCMS so they can magically edit content with Claude MCP.
Shop with @vendure_io
REALLY fun stack to use.
cavetourneegenerale.com/
Bastien retweeted
The Gridy leaderboard is live.
Your first 1,000 solo Gridy bets this week are your run. Bet size doesn't score, only the odds do. The three best finished runs win $50, $25 and $10.
Week 1 closes Monday 00:00 UTC.
app.lynx.finance/arcade/lead…
When you build a cooking app and you can dress @posthog RoboHog to really be part of the team.
VERY important feature.
1
5
269
Bastien retweeted
Someone behind the software
I think good products carry something of the people who make them. Their experience, what they care about, and how they think things should work. You might not know who those people are, but you can feel their perspective in the product.
The industry often talks about software as though it comes out of a factory. You collect requirements, build features, and measure whether they work. Follow the process and you should get a good result. Now we're talking automating this whole pipeline with agents.
But two teams can talk to similar customers, have access to the same technology, and make very different things. The difference comes from how they understand what they see and the style they go about building it. The founder background or company DNA also shapes this a lot.
At Linear, we have always valued intuition over process or data. I think people sometimes understand that as making decisions based on personal preference, without much thought or evidence. What we mean by it that your intuition develops through experience and understanding. You work on something, talk to customers, make mistakes, and learn what to pay attention to. The intuition is your point of view on something, and forcing to use your judgment, not hide behind faceless data.
Before we launched, we talked to people across companies and roles about how they worked. We had our own frustrations with this type software, but those conversations helped us understand what mattered beyond our own experience. Our perspective got better after those conversations.
So eventually the products develops a character through what its makers pay attention to, what they decide not to do and what they keep working on after it technically works. I sometimes think of this as the soul of a product. You feel that someone cares about how the whole thing comes together.
A feature can work perfectly well on its own and still make the product worse. Recognizing that requires some belief about what the product should be. Someone has to make the call, then stay close enough to customers to see whether they were right.
Recently, many products are starting to feel messy to me, including products from very successful companies. There seems to be more thought going into what the technology can do and what can be added than the form it should take. The product changes are primarily additive, not improving the core problem.
I think the reasons for this is that it's lot easier to add new capabilities, than rethink existing capabilities. So each product becomes a collection of abilities, without actually having unified point of view.
I wonder whether some of this comes from how the work is organized. Individuals work with agents to produce changes independently, each operating a small software factory. Each change might make sense on its own, but together they start to resemble Frankenstein’s monster rather than a carefully shaped sculpture.
Without the shared perspective,
soul, or thought, the product becomes an average of all those outputs. The choices that once gave it character are being diluted by day. More things work, but it becomes harder to feel someone or even something behind them.
Making software is getting easier. I hope that gives people more room to develop a perspective and follow it further. To understand a problem deeply and keep shaping an answer until the pieces belong together.
I want to feel the creator behind the software, not the factories.
New on the blog:
— Someone behind the software
I think good products carry something of the people who make them
karrisaarinen.com/posts/some…
Bastien retweeted
stop selling to indiehackers
build software for companies already making money
a successful startup/company is not interested in vibe coding everything; they want stuff to work
they don't mind paying saas prices for things that add value
indiehackers will spend days replacing software to save $50/m (and that is totally fine)
yes a lot of internal tooling will be vibe coded, but there is so much opportunity right now to build software that just works and within an agent stack
i am a really big fan of building things in house (especially with ai now) but we are growing fast and we have no time to waste; we are not trying to save a few hundred $ a month
everything is moving faster, growing startups don't want to waste any time


















