Dorian Becker (@blaked_84) header
Dorian Becker (@blaked_84) profile picture

I do stuff with computers. CTO & Co-founder @evalmeeHQ - @daily_ruby_tips

Paris
Joined November 2015
Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)Photo by Dorian Becker (@blaked_84)
Porting @benjitaylor's agentation.dev to Vue.js 👀 Annotate your UI, get Vue component names + context, ready to paste to your AI agent. No more screenshots eating your token budget.
1
3
309
Le rĂ©veil risque d’ĂȘtre brutal... Je viens de regarder une audition de Luc Ferry, Laurent Alexandre et Olivier Babeau sur l’IA, l’école, le travail et ce qui nous attend... Je ne prends pas toutes leurs prĂ©dictions pour des certitudes, personne ne sait exactement Ă  quoi ressemblera le marchĂ© du travail dans 5 ou 10 ans. Mais sur le fond, je partage totalement leur inquiĂ©tude : on est beaucoup trop lents... Ca fait plus de 30 ans que je travaille sur le terrain. Commerce, distribution, restauration, immobilier. J’ai recrutĂ©, formĂ©, managĂ©, vendu, dirigĂ© des Ă©quipes, vu des organisations fonctionner et d’autres se planter. Et ce que je vois aujourd’hui avec l’IA n’a rien d’un simple changement d’outil. Le problĂšme, ce n’est dĂ©jĂ  plus de savoir si ChatGPT, Claude ou autre peut nous faire gagner du temps. Le problĂšme, c’est que les capacitĂ©s progressent plus vite que notre capacitĂ© Ă  adapter les mĂ©tiers, les entreprises, l’école et parfois mĂȘme notre maniĂšre de rĂ©flĂ©chir. Pendant longtemps, on a rĂ©pĂ©tĂ© : "l’IA ne remplacera pas les humains, les humains qui utilisent l’IA remplaceront ceux qui ne l’utilisent pas". J’ai moi-mĂȘme souvent dĂ©fendu cette idĂ©e. Aujourd’hui, j’y mets une Ă©norme nuance. Utiliser une IA ne suffit pas. Appuyer sur un bouton ne crĂ©e pas de valeur. Donnez exactement le mĂȘme outil Ă  deux personnes. L’une saura poser le bon problĂšme, donner le contexte, dĂ©tecter une incohĂ©rence, challenger la rĂ©ponse, la remettre dans la rĂ©alitĂ© du terrain et dĂ©cider. L’autre recopiera ce qui sort. MĂȘme IA. Deux rĂ©sultats complĂštement diffĂ©rents. Et c’est lĂ  que je trouve le sujet de l’éducation inquiĂ©tant. Si on apprend Ă  nos gamins Ă  dĂ©lĂ©guer leur rĂ©flexion avant mĂȘme de leur avoir appris Ă  rĂ©flĂ©chir, on ne crĂ©e pas une gĂ©nĂ©ration augmentĂ©e par l’IA. On crĂ©e une gĂ©nĂ©ration dĂ©pendante de l’IA. Lire. Écrire. Comprendre rĂ©ellement un texte. Argumenter. Avoir de la culture gĂ©nĂ©rale. Savoir reconnaĂźtre quand quelque chose paraĂźt absurde. Savoir poser une bonne question parce qu’on comprend le problĂšme. Tout ça devient encore plus important quand une machine peut vous produire en quelques secondes une rĂ©ponse brillante en apparence. Plus l’outil devient puissant, plus le discernement devient prĂ©cieux. Et sur le travail, on continue Ă  se rassurer avec l’histoire des prĂ©cĂ©dentes rĂ©volutions industrielles. "Des mĂ©tiers vont disparaĂźtre, mais d’autres seront créés." Peut-ĂȘtre. Mais cette fois il y a une diffĂ©rence Ă©norme : l’IA ne touche pas seulement des tĂąches rĂ©pĂ©titives ou physiques, elle touche directement des tĂąches cognitives qu’on pensait rĂ©servĂ©es aux gens formĂ©s, diplĂŽmĂ©s, expĂ©rimentĂ©s. Traduction. DĂ©veloppement. Graphisme. Analyse. RĂ©daction. Recherche. Conseil. Juridique. MĂ©decine. StratĂ©gie. Et il faut arrĂȘter de croire que les nouveaux mĂ©tiers créés autour de l’IA seront automatiquement protĂ©gĂ©s. L’IA suivante pourra aussi venir en automatiser une partie. Ça ne veut pas dire que tout le monde sera au chĂŽmage dans cinq ans. Je n’en sais rien et personne ne le sait. Mais croire que tout cela aura un impact marginal sur l’emploi me paraĂźt tout aussi dĂ©connectĂ©. La vraie question, c’est : qu’est-ce qu’on apprend encore Ă  faire nous-mĂȘmes, qu’est-ce qu’on dĂ©lĂšgue, et surtout comment on reste capable de comprendre, contrĂŽler et dĂ©cider quand la machine fait une part croissante du travail ? Et lĂ , notre lenteur devient dangereuse. Parce que la technologie n’attendra pas que l’Éducation nationale ait fini de réécrire ses programmes. Elle n’attendra pas que les entreprises aient terminĂ© leurs comitĂ©s de rĂ©flexion. Elle n’attendra pas que les politiques aient compris ce qu’est un agent IA. Elle avance. Avec nous ou sans nous. Il y a aussi un problĂšme europĂ©en derriĂšre tout ça. On adore parler rĂ©glementation. TrĂšs bien. Il faut des rĂšgles. Mais pendant ce temps-lĂ , les modĂšles, les puces, les infrastructures et une Ă©norme partie de l’innovation sont dĂ©veloppĂ©s ailleurs. RĂ©glementer une technologie que d’autres possĂšdent, dĂ©veloppent et maĂźtrisent mieux que nous, ce n’est pas ĂȘtre souverain. C’est ĂȘtre dĂ©pendant avec un rĂšglement intĂ©rieur. Et au milieu de tout ça, je reste convaincu d’une chose : l’humain garde quelque chose que la machine n’a pas. Les valeurs. La responsabilitĂ©. Le choix. La dĂ©cision. Une IA peut produire une rĂ©ponse. Elle peut argumenter. Elle peut simuler une position morale. Elle peut mĂȘme ĂȘtre meilleure que moi sur Ă©normĂ©ment de tĂąches. Mais elle ne vit pas avec les consĂ©quences de la dĂ©cision. Moi, oui. C’est pour ça que je refuse autant le discours "l’IA va tout rĂ©gler" que le discours "il faut protĂ©ger l’humain de l’IA". Il faut surtout prĂ©parer l’humain Ă  vivre et travailler avec quelque chose qui devient extraordinairement puissant. Et ça demande beaucoup plus que trois prompts trouvĂ©s sur LinkedIn. Ça demande de la culture, du travail, de la curiositĂ©, de l’esprit critique, la comprĂ©hension du rĂ©el, et surtout la capacitĂ© Ă  dĂ©cider. Avec mes 30 ans de terrain, c’est probablement ça qui me frappe le plus aujourd’hui. Je ne vois pas une technologie qui supprime l’expĂ©rience. Je vois une technologie qui rend l’expĂ©rience encore plus exploitable pour ceux qui en ont, et qui peut devenir un piĂšge Ă©norme pour ceux qui dĂ©lĂšguent avant d’avoir appris. Je me fiche de savoir quel modĂšle est numĂ©ro 1 cette semaine. Le vrai sujet, c’est : est-ce qu’on apprend assez vite ? Et lĂ , j’ai de sĂ©rieux doutes. Le rĂ©veil risque d’ĂȘtre brutal. Pas parce que l’IA va nous attaquer. Parce qu’elle avance beaucoup plus vite que notre capacitĂ© collective Ă  comprendre ce qu’elle change. VidĂ©o complĂšte en lien. Elle est longue, parfois provocatrice, certaines prĂ©dictions sont discutables. Mais elle mĂ©rite d’ĂȘtre regardĂ©e. Surtout si vous n’ĂȘtes pas d’accord...
33
44
5
159
19,061
Dorian Becker 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.
145
59
46
1,250
100,357
Dorian Becker retweeted
New on the blog: — Our organizations are being DDoSed from the inside I’ve written before that you can outsource work, but not your understanding. As a CEO, I’m finding that harder to live up to. It feels like our organizations are being DDoSed from the inside. Nobody is trying to overwhelm the company. Everyone is doing something they think is useful. Leaders never saw every piece of work. But now the work can change the company’s direction faster than anyone can follow. It’s like a car speeding up until it becomes impossible to steer. I think lot of leaders are stepping back now and letting the things happen. But stepping back doesn’t remove my responsibility for where this all leads. Are other leaders feeling this? How do you deal with it?
39
20
14
400
33,596
Dorian Becker retweeted
À force de dĂ©construire la hustle culture, on a presque rĂ©ussi Ă  rendre honteuse l'idĂ©e qu'une ambition extraordinaire puisse demander un effort extraordinaire. Et je trouve ça assez amusant. Il y a quelques annĂ©es, on glorifiait le travail jusqu'Ă  l'absurde. Dormir quatre heures. Travailler tous les week-ends. RĂ©pondre Ă  ses mails Ă  2h du matin. Faire du burn-out un signe extĂ©rieur d'ambition. C'Ă©tait dĂ©bile. Alors on a corrigĂ©. Et comme souvent, on a corrigĂ© trop fort. Aujourd'hui, on parle de leverage. De systĂšmes. De talent. De rĂ©seau. De chance. D'IA. Tout ça compte Ă©normĂ©ment. Mais rien de tout ça ne change une rĂ©alitĂ© assez inconfortable : il n'existe probablement aucune version de votre vie oĂč vous accomplirez quelque chose d'extraordinaire sans travailler extraordinairement dur. Le problĂšme, c'est qu'on confond travailler dur et travailler beaucoup. Ce n'est pas la mĂȘme chose. Vous pouvez travailler 100 heures par semaine sur le mauvais problĂšme. Vous aurez Ă©normĂ©ment travaillĂ©. Vous n'aurez pas nĂ©cessairement travaillĂ© dur. Travailler dur, c'est rester sur un problĂšme quand la rĂ©ponse Ă©vidente ne fonctionne pas. Recommencer quelque chose que vous pensiez avoir terminĂ© parce que ce n'est pas assez bon. Apprendre ce que vous ne savez pas faire. Accepter que votre premiĂšre idĂ©e Ă©tait mauvaise. RĂ©pĂ©ter. Corriger. Et rester assez longtemps pour devenir bon. Je me suis toujours demandĂ© si les gens exceptionnellement intelligents pouvaient accomplir de grandes choses sans vraiment travailler dur. Et aprĂšs avoir passĂ© ma vie entourĂ© de gens exceptionnellement intelligents, mon constat est assez simple : non. Le talent aide. L'intelligence aide. Le rĂ©seau aide. La chance aide Ă©normĂ©ment. Le leverage multiplie votre travail. L'IA aussi. Mais pour multiplier quelque chose, il faut d'abord qu'il y ait quelque chose Ă  multiplier. Et ceci ne veut pas dire glorifier la souffrance. Être Ă©puisĂ© n'est pas une preuve d'ambition. Être occupĂ© n'est pas une preuve de travail. Et travailler Ă©normĂ©ment sur le mauvais problĂšme reste une trĂšs mauvaise idĂ©e. Mais l'excĂšs inverse est tout aussi absurde. Si vous voulez accomplir quelque chose que trĂšs peu de gens accomplissent, il faudra probablement accepter de faire des efforts que trĂšs peu de gens acceptent de faire. Le travail ne garantit pas le succĂšs. Mais pour certaines ambitions, il reste le prix d'entrĂ©e.
20
18
7
180
17,532
Dorian Becker retweeted
The idea of "one shotting" an app using AI is a fugazi. If you had to describe my app and all the edge cases I have solved over the years, it would be a prompt the size of a small book, and my app isn't even that complicated. The people promoting creating a business overnight with AI are just selling a get rich quick pipedream. Those grifters are present in every cycle. AI has completely transformed how I work, but you can't push a button and make money. Doesn't work like that.
Talking to smarter folks than me, I'm convinced many of the AI folks in my timeline are full of shit. Nobody is "running 20 agents over night" and building stuff for actual users. Maybe some are building internal tools or disposable software. Maybe. But building software people like using? That doesn't get hacked on day one or blow up after the 3rd user? Nope. I don't even understand what that's supposed to look like. Do you work out a 57 pages document that perfectly describes what you want to build and then summon 14 agents and have them run wild for 6 hours? And what comes out on the other end isn't a broken pile of shit? Nope. Not buying it. PS: it may also be that I have an IQ of 82 and can't figure it out.
254
299
73
3,727
405,823
Dorian Becker retweeted
Every project needs OG images and a favicon set. nobody wants to make them. metadata-gen scans your repo — colors, logo, title — and generates the whole set locally. no API keys, no upload. npx metadata-gen init
11
13
345
23,805
Agitation-vue is now live in the Chrome Web Store agentation-vue.beckr.fr/
73
Dorian Becker retweeted
Shoe company Allbirds just announced that it's planning to - Sell all of its brands and footwear assets - Rebrand the company to Newbird AI - Use a $50M convertible financing facility to "acquire high-performance GPU assets"
329
130
422
3,153
1,979,221
Quick poll: Which app do you use daily that has a built-in agent? Here are the one I uses: @linear, @posthog, @NotionHQ, @pendev. Tell me yours !
122
Claude Code just crushed a complex query I was building for a new feature: I handed it a realistic dataset + the ability to run real queries itself. Instructed it to loop, test multiple strategies, and build comparison tables. It iterated until it found the winner. 50x performance gain. I didn’t optimize the query. I just gave the AI the keys to the lab.
89
Dorian Becker retweeted
Introducing Fluid Functionalism, open source ui components where every hover, transition, and animation serves a purpose. Built on top of shadcn/ui and radix. One CLI command to install. Link ↓
39
35
2
947
68,359
Here’s the dictation hack that removed the awkwardness for me: I’ve never enjoyed using voice tools because speaking aloud to my computer in public felt strange. @WisprFlow + a simple lavalier mic on my collar made it click. Whisper or speak normally, it just works incredibly well.
1
1
197
Agitation-vue is now pending validation on the Google Chrome Web Store đŸ€ž
63
Referencing another annotation
94
Agentation-vue can now be activated with a long key press or a double tap
88
Dorian Becker retweeted
Every step has been predicted by ai-2027.com for more than a year Now, there’s one more
Introducing Project Glasswing: an urgent initiative to help secure the world’s most critical software. It’s powered by our newest frontier model, Claude Mythos Preview, which can find software vulnerabilities better than all but the most skilled humans. anthropic.com/glasswing
2
1
1
10
2,682
Here’s what changed: Refactoring, edge-case hunting, and migrating legacy code to the winning pattern used to cost a fortune in time. Now? A fraction of what it did. The best builders are cashing in, not to ship faster, but to ship better: cleaner, more reliable products that users trust and keep coming back to. The era of ‘fast and fragile’ is over. The era of affordable excellence for users just began.
sent this to the team today everything great comes from being able to delay gratification for as long as possible and it feels like we're collectively losing our ability to do that
215
Dorian Becker retweeted
I think we have lost some sense of judgment and moderation when it comes to product building currently. The moment you turn something into a universally celebrated metric, whether that is token burn, prototype count, or percentage of agent-written code, you start losing sight of what actually matters. I have felt the same way for a long time about overusing data and A/B testing to build products. The moment you reduce product quality or productivity to a metric, you stop shipping value and start shipping numbers. A lot of what people are doing with AI makes directional sense. The missing piece is counterbalance: 1. AI should help engineers build better products. Leaderboards and adoption metrics can be useful as directional signals. They do not tell you what is being built, whether it is good, or whether it should exist at all. 2. Users do not care what percentage of your code was written by agents. They care about the outcome. Faster output is useful. Like usually, faster doesn't seem to add to quality, clarity, or stability of products. Power to build should not become an excuse to lower quality bars. 3. LLM-generated prototypes can feel like late-night whiteboarding sessions. They look exciting in the moment and feel productive very quickly. Then a few days later you realize the idea was shallow, distracting, or simply wrong. The same trap shows up in jumping straight to code and solutions more broadly. You may just be building the wrong thing more efficiently. Prototyping has its place. So do clear thinking, good design, and a real understanding of the user’s problem. In terms of activities or momentum, the main quest and the side quest can both feel productive but only one actually moves the mission forward. 4. Adding more to products is still dangerous as ever even if time or effort to add it has gone down. Every addition creates complexity, maintenance cost, and user confusion. New features should be pushed back unless they clearly show it should exist and how it improves the product. 5. Not everything needs to be an agent shaped. A simple scheduled task does not need a full LLM sandbox. Making something agentic because it feels current or impressive does not make it right-sized, correct, or effective. The core ideas are: - even if you can, maybe you should not. - more power we have to build should not reduce our need to think, it should increase it.
sent this to the team today everything great comes from being able to delay gratification for as long as possible and it feels like we're collectively losing our ability to do that
29
123
30
1,047
151,999