Fabien Devos

3K posts

Fabien Devos banner
Fabien Devos

Fabien Devos

@Fabien_Devos

CTO and co-founder @vybe_build (YC X25) . Co-founder @wolfia_app (YC S22). Ex @wealthfront and @facebook. Co-creator of @hacked_app.

San Francisco Katılım Mart 2010
423 Takip Edilen1.6K Takipçiler
Sabitlenmiş Tweet
Fabien Devos
Fabien Devos@Fabien_Devos·
Super happy to announce that @vybe_build is now open for anyone to use! We are also thrilled to announce that we raised $10M with First Round to make it easy to build secure internal apps with AI.
Quang HOANG@qhoang09

Today we’re launching Vybe to the world and announcing our $10M Seed round to make vibe-coding actually work inside companies. This is why, how and our vision: Over the last few decades, every fast-growing company has quietly built the same mess behind the scenes: internal ops glued together with rigid SaaS, fragile spreadsheets or custom-coded tools nobody wants to maintain. Meanwhile, eng teams are stretched thin. Internal tools never make it to the top of the backlog. Vibe-coding is changing the game but it’s mostly been good for prototypes, landing pages, and side projects disconnected to production data. Our belief is simple: in the next few years, most internal software will be vibe-coded by teams working with AI, engineers and business teams together. Vybe is built for that collaboration: 1/ Business teams own the surface area:  Business teams (Ops, CX, PMs etc.)  can build and iterate on apps themselves: flows, UI, fields, and logic; without waiting weeks for eng to pick up another “internal tools” ticket. 2/ Engineers own the foundation:  Integrate production data (Postgres, Salesforce, Jira, and 3,000 integrations), define SQL definitions once, set up SSO auth, access control, and keep everything in Git to help when needed (from their favorite IDE!) 3/ Secure by design:  Our security and permissioning layer is not vibe-coded and can’t be modified by AI. Everyone can sleep at night. 4/ Team-ready out of the box:  SSO, Auth, environments, deployments, and review flows are built in. Over the last few months, we’ve been in closed waitlist mode and have hand-onboarded teams to pressure-test Vybe on real production workflows: - A YC Founder runs his entire CS operation on Vybe and saves ~2 days per week. - Another company ingested millions of rows from their warehouse to build BI-like internal views that would break typical AI builders. - One team fully replaced Metabase/Looker by plugging Redshift into Vybe and just… prompting their way to MAU, DAU, funnels… Remix apps from world-class operators To make it even easier to get started, we’re launching templates co-created with operators who’ve already solved these problems at scale: - @collinmathilde (CEO @ Front) – how she runs 1:1s - @lenny (yeah, that Lenny!) - how to manage up, do perf reviews and write PRDs - @sushmars (CTO @ 23andMe) - her  7Cs Framework for Build vs. Buy Decisions - and many more from the best Tech leaders Backed by people who’ve lived this pain We’ve raised $10M in Seed funding, led by @firstround with participation from @ycombinator and an incredible group of operators and founders, including: The CEO Datadog, CEO Grammarly, CEO Reforge, CTO Intercom, Head of Product at OpenAI, Head of Product Anthropic, and 50 more incredible operators who believed in our vision! Huge thank you to our early customers, team, and investors for believing in us this early. 🙏 We’re now in GA: no more waitlist! vybe.build

English
3
0
5
417
Quang HOANG
Quang HOANG@qhoang09·
OpenClaw is now the #1 software project on GitHub with 247k stars (React has 243k)
Quang HOANG tweet media
English
3
0
3
154
Michael Seibel
Michael Seibel@mwseibel·
Building my own AI personal assistant is hard but more fun than I could have imagined :)
English
82
6
371
26.1K
Fabien Devos retweetledi
Quang HOANG
Quang HOANG@qhoang09·
I am automating our changelogs using @vybe_build: 1/ Connect to @github to check merged PRs 2/ Select PRs in @vybe_build dashboard 3/ Generate changelog on vybe.build/changelog automatically 4/ Also generate drafts for Linkedin and X 5/ Currently testing out @Remotion for videos Still some work to do but it's starting to look good
English
2
2
4
445
Fabien Devos retweetledi
Quang HOANG
Quang HOANG@qhoang09·
I'll be sharing regularly what we've been working on. Last week was one of those very productive weeks at @vybe_build Vybe Changelog v1.1.0: - AI suggestions for next steps as you're building - Forkable app templates from best operators - Smoother workflows in natural language (e.g. Send me this pipeline numbers in Slack every day at 8AM) - 20+ New integration actions: Attio, Stripe, Gemini, HubSpot, Salesforce, Supabase, Linear, and more Way to go, @Fabien_Devos and @vybe_build team 🚀
English
1
1
8
217
Fabien Devos retweetledi
Quang HOANG
Quang HOANG@qhoang09·
Every CS/sales leader I talk to loses like an hour per call in followup busywork (notes, CRM updates, emails to customers, team messages). It's brutal Joe Schmitt (SVP Customer support at @OnUpKeep) has got that down to only 5 minutes using @vybe_build We're hosting a small event (Feb 4 in SF) where he'll show you how he did it (and you build the same for free). Join us! vybe.build/events/ship-it…
English
1
3
6
184
Fabien Devos retweetledi
Quang HOANG
Quang HOANG@qhoang09·
Saw a video of @satyanadella saying: “SaaS are CRUD databases with business logic. As AI takes over that logic, SaaS will collapse.” I don’t agree with the conclusion, but I think the quote points to something real about how AI is changing the shape of SaaS. Thread 👇 youtube.com/watch?v=a_RjOh…
YouTube video
YouTube
English
2
5
8
1K
Fabien Devos retweetledi
Tim Sweeney
Tim Sweeney@TimSweeneyEpic·
The 9th Circuit Court has confirmed: The Apple Tax is dead in the USA. Apple can require side-by-side placement of Apple payments and developer payments, as Fortnite does. And Apple can collect fees for actual costs of facilitating links and IP associated with links.
English
106
179
2.6K
947.3K
Fabien Devos retweetledi
Nicolas Dessaigne
Nicolas Dessaigne@dessaigne·
"If you want to build a website, use Lovable. But if you want to build robust internal applications, use Vybe." Couldn’t sum it up better, Vybe is nailing the next generation of internal tools! Huge congrats to @qhoang09, @Fabien_Devos and the whole @vybe_build team for this launch and their $10M seed round 💥🚀
Quang HOANG@qhoang09

Today we’re launching Vybe to the world and announcing our $10M Seed round to make vibe-coding actually work inside companies. This is why, how and our vision: Over the last few decades, every fast-growing company has quietly built the same mess behind the scenes: internal ops glued together with rigid SaaS, fragile spreadsheets or custom-coded tools nobody wants to maintain. Meanwhile, eng teams are stretched thin. Internal tools never make it to the top of the backlog. Vibe-coding is changing the game but it’s mostly been good for prototypes, landing pages, and side projects disconnected to production data. Our belief is simple: in the next few years, most internal software will be vibe-coded by teams working with AI, engineers and business teams together. Vybe is built for that collaboration: 1/ Business teams own the surface area:  Business teams (Ops, CX, PMs etc.)  can build and iterate on apps themselves: flows, UI, fields, and logic; without waiting weeks for eng to pick up another “internal tools” ticket. 2/ Engineers own the foundation:  Integrate production data (Postgres, Salesforce, Jira, and 3,000 integrations), define SQL definitions once, set up SSO auth, access control, and keep everything in Git to help when needed (from their favorite IDE!) 3/ Secure by design:  Our security and permissioning layer is not vibe-coded and can’t be modified by AI. Everyone can sleep at night. 4/ Team-ready out of the box:  SSO, Auth, environments, deployments, and review flows are built in. Over the last few months, we’ve been in closed waitlist mode and have hand-onboarded teams to pressure-test Vybe on real production workflows: - A YC Founder runs his entire CS operation on Vybe and saves ~2 days per week. - Another company ingested millions of rows from their warehouse to build BI-like internal views that would break typical AI builders. - One team fully replaced Metabase/Looker by plugging Redshift into Vybe and just… prompting their way to MAU, DAU, funnels… Remix apps from world-class operators To make it even easier to get started, we’re launching templates co-created with operators who’ve already solved these problems at scale: - @collinmathilde (CEO @ Front) – how she runs 1:1s - @lennysan (yeah, that Lenny!) - how to manage up, do perf reviews and write PRDs - @sushmars (CTO @ 23andMe) - her  7Cs Framework for Build vs. Buy Decisions - and many more from the best Tech leaders Backed by people who’ve lived this pain We’ve raised $10M in Seed funding, led by @firstround with participation from @ycombinator and an incredible group of operators and founders, including: The CEO Datadog, CEO Grammarly, CEO Reforge, CTO Intercom, Head of Product at OpenAI, Head of Product Anthropic, and 50 more incredible operators who believed in our vision! Huge thank you to our early customers, team, and investors for believing in us this early. 🙏 We’re now in GA: no more waitlist! vybe.build

English
7
11
122
67.6K
Fabien Devos
Fabien Devos@Fabien_Devos·
@qhoang09 Amazing job by our incredible team! Super proud of them.
English
0
0
1
215
Quang HOANG
Quang HOANG@qhoang09·
Today we’re launching Vybe to the world and announcing our $10M Seed round to make vibe-coding actually work inside companies. This is why, how and our vision: Over the last few decades, every fast-growing company has quietly built the same mess behind the scenes: internal ops glued together with rigid SaaS, fragile spreadsheets or custom-coded tools nobody wants to maintain. Meanwhile, eng teams are stretched thin. Internal tools never make it to the top of the backlog. Vibe-coding is changing the game but it’s mostly been good for prototypes, landing pages, and side projects disconnected to production data. Our belief is simple: in the next few years, most internal software will be vibe-coded by teams working with AI, engineers and business teams together. Vybe is built for that collaboration: 1/ Business teams own the surface area:  Business teams (Ops, CX, PMs etc.)  can build and iterate on apps themselves: flows, UI, fields, and logic; without waiting weeks for eng to pick up another “internal tools” ticket. 2/ Engineers own the foundation:  Integrate production data (Postgres, Salesforce, Jira, and 3,000 integrations), define SQL definitions once, set up SSO auth, access control, and keep everything in Git to help when needed (from their favorite IDE!) 3/ Secure by design:  Our security and permissioning layer is not vibe-coded and can’t be modified by AI. Everyone can sleep at night. 4/ Team-ready out of the box:  SSO, Auth, environments, deployments, and review flows are built in. Over the last few months, we’ve been in closed waitlist mode and have hand-onboarded teams to pressure-test Vybe on real production workflows: - A YC Founder runs his entire CS operation on Vybe and saves ~2 days per week. - Another company ingested millions of rows from their warehouse to build BI-like internal views that would break typical AI builders. - One team fully replaced Metabase/Looker by plugging Redshift into Vybe and just… prompting their way to MAU, DAU, funnels… Remix apps from world-class operators To make it even easier to get started, we’re launching templates co-created with operators who’ve already solved these problems at scale: - @collinmathilde (CEO @ Front) – how she runs 1:1s - @lennysan (yeah, that Lenny!) - how to manage up, do perf reviews and write PRDs - @sushmars (CTO @ 23andMe) - her  7Cs Framework for Build vs. Buy Decisions - and many more from the best Tech leaders Backed by people who’ve lived this pain We’ve raised $10M in Seed funding, led by @firstround with participation from @ycombinator and an incredible group of operators and founders, including: The CEO Datadog, CEO Grammarly, CEO Reforge, CTO Intercom, Head of Product at OpenAI, Head of Product Anthropic, and 50 more incredible operators who believed in our vision! Huge thank you to our early customers, team, and investors for believing in us this early. 🙏 We’re now in GA: no more waitlist! vybe.build
English
32
30
143
107K
Fabien Devos
Fabien Devos@Fabien_Devos·
It's especially important to remember that LLMs have no long term memory. So they're very much like in Memento: wake up in the dark with no idea what they're here for and all they can see are a bunch of post it notes.
Andrej Karpathy@karpathy

Something I think people continue to have poor intuition for: The space of intelligences is large and animal intelligence (the only kind we've ever known) is only a single point, arising from a very specific kind of optimization that is fundamentally distinct from that of our technology. Animal intelligence optimization pressure: - innate and continuous stream of consciousness of an embodied "self", a drive for homeostasis and self-preservation in a dangerous, physical world. - thoroughly optimized for natural selection => strong innate drives for power-seeking, status, dominance, reproduction. many packaged survival heuristics: fear, anger, disgust, ... - fundamentally social => huge amount of compute dedicated to EQ, theory of mind of other agents, bonding, coalitions, alliances, friend & foe dynamics. - exploration & exploitation tuning: curiosity, fun, play, world models. LLM intelligence optimization pressure: - the most supervision bits come from the statistical simulation of human text= >"shape shifter" token tumbler, statistical imitator of any region of the training data distribution. these are the primordial behaviors (token traces) on top of which everything else gets bolted on. - increasingly finetuned by RL on problem distributions => innate urge to guess at the underlying environment/task to collect task rewards. - increasingly selected by at-scale A/B tests for DAU => deeply craves an upvote from the average user, sycophancy. - a lot more spiky/jagged depending on the details of the training data/task distribution. Animals experience pressure for a lot more "general" intelligence because of the highly multi-task and even actively adversarial multi-agent self-play environments they are min-max optimized within, where failing at *any* task means death. In a deep optimization pressure sense, LLM can't handle lots of different spiky tasks out of the box (e.g. count the number of 'r' in strawberry) because failing to do a task does not mean death. The computational substrate is different (transformers vs. brain tissue and nuclei), the learning algorithms are different (SGD vs. ???), the present-day implementation is very different (continuously learning embodied self vs. an LLM with a knowledge cutoff that boots up from fixed weights, processes tokens and then dies). But most importantly (because it dictates asymptotics), the optimization pressure / objective is different. LLMs are shaped a lot less by biological evolution and a lot more by commercial evolution. It's a lot less survival of tribe in the jungle and a lot more solve the problem / get the upvote. LLMs are humanity's "first contact" with non-animal intelligence. Except it's muddled and confusing because they are still rooted within it by reflexively digesting human artifacts, which is why I attempted to give it a different name earlier (ghosts/spirits or whatever). People who build good internal models of this new intelligent entity will be better equipped to reason about it today and predict features of it in the future. People who don't will be stuck thinking about it incorrectly like an animal.

English
1
0
3
225