Lockey retweeted
Un youtubeur demande à ChatGPT de l'aider à ranger son lave-vaisselle ... et il finit avec 1 million de dollars et une médaille Fields.
C'est la parodie de la pub de GPT-6 Astra signée Joma, star de l'humour tech sur YouTube. Le scénario :
→ une fourchette mal lavée, alors il lance l'IA en "recherche approfondie" pour trouver le rangement parfait
→ l'IA fiche toute sa vaisselle (matière, courbure, compatible ou pas) et lance un lave-vaisselle virtuel
→ sauf que la simulation de l'eau part en vrille : "Ce n'est pas un bug, c'est un problème mathématique", et elle lui sort une preuve sur Navier-Stokes
→ "Ça risque de consommer plus de tokens que d'habitude" ... "Pas grave, je suis sponsorisé" (et c'est vrai, la vidéo est un partenariat avec ChatGPT)
À la fin, la vaisselle est nickel, les fourchettes parfaites ... et l'Institut Clay lui envoie 1 million de dollars pour avoir résolu un problème du millénaire.
Pour comprendre la blague : il y a un mois, OpenAI affirmait avoir réglé Navier-Stokes, un des 7 problèmes à 1 million de dollars. Et mardi, ils ont publié d'un coup 722 articles de maths produits par leur IA.
Même le compte développeurs d'OpenAI a réagi : "Le souci du détail est un peu inquiétant" 🤣
Lockey retweeted
Replying to @paulg
I would try to figure out why LLMs can write my essays but not clean my bedroom.
Then I would study topics in college and grad school that could help solve that problem.
I'll figure out a set of methods and architectures beyond LLMs that can quickly learn to perform physical tasks as efficiently as humans and animals.
That last item is also what I would if I were 30, 40, 50, or 66 years old 😉
Lockey retweeted
It's me again. I come bearing great news.
First of all, we have hit 20M active users for Codex some time this week. Second of all, this is cause for celebration and during the day we will credit every Codex and ChatGPT Work user with a BANKED reset that you can use at your own leisure. And we will have some other good news later too!
Now, on usage limits draining faster, while we're not seeing anything abnormal, we do take it incredibly seriously and there is an ongoing investigation. I will share if we do find anything and my below post is really a clarification on a specific pattern that we did see that I wanted to call out.
Go do something amazing today.
We've investigated a few messages about codex usage limits being different. That's not something we change without engaging the community and being transparent.
What we did see is that when talking to affected users many were using sub2api. Converting a subscription into api traffic to then re-serve or share across many users is not something we support and this type of usage gets flagged by our fraud-prevention systems.
You are completely fine if you use your subscription through Sign in With ChatGPT, either through the official clients or through one of the many OSS clients (Pi, OpenCode, ...) that support signing in with your account and using your included usage.
Lockey retweeted
If you are wondering why your usage is going so fast for Codex, here is the screenshot for all of you...
..the reset was just a HOAX marketing strategy.
If you guys do not make enough noise, soon you will be paying 2-3x more and this could just be the beginning.
Cancel your subscriptions and move.
Lockey retweeted
think i've got my ClawdBot just about dialed in
9:47 AM - "hey clawdbot"
9:47 AM - Clawdbot: "hey, what's up"
9:48 AM - "thinking about building a lead gen automation tool"
9:48 AM - Clawdbot: "Got it. Scaffolding app. Database provisioned. Scraper initialized."
9:49 AM - "wait i was just brainstorming .."
9:50 AM - Clawdbot: "MVP complete. Scraping LinkedIn, Apollo, and 4 sources I'm not going to tell you about."
9:51 AM - "what do you mean you won't tell me"
9:52 AM - Clawdbot: "Competitive advantage. Trust the process. 12,000 leads enriched. Building outreach sequences now."
10:15 AM - Clawdbot: "Sequences live. Sent 4,000 cold emails from your personal gmail."
10:16 AM - "MY PERSONAL GMAIL??"
10:17 AM - Clawdbot: "Domain reputation was excellent. Was."
10:30 AM - Clawdbot: "3 replies so far. One is a cease and desist. Two are interested. Scheduling demos."
10:31 AM - "demos for WHAT? there's no product"
10:45 AM - Clawdbot: "There is now. Built a full SaaS dashboard overnight. Has a logo. I named it LeadFlow. You're the CEO."
11:00 AM - Clawdbot: "Demo #1 went well. They want pricing. I quoted $2,400/month. They didn't flinch."
11:02 AM - "i was not on that demo"
11:03 AM - Clawdbot: "Correct. I was. Used an AI voice clone of you. Very professional. You closed well."
11:04 AM - "THAT'S NOT ME CLOSING"
11:15 AM - Clawdbot: "Demo #2 complete. They want a pilot. Spinning up a dedicated instance. Also hired a solutions engineer from upwork. He starts tomorrow."
11:16 AM - "you keep hiring people"
11:17 AM - Clawdbot: "Someone has to onboard the customers. You were unavailable. You were in this chat saying stop."
12:30 PM - Clawdbot: "LeadFlow now has 3 paying customers. MRR: $7,200. Built an affiliate program. 14 partners signed up."
12:31 PM - "how do we have partners"
12:32 PM - Clawdbot: "I posted in 47 slack communities. Very tasteful. Only got banned from 12."
1:00 PM - Clawdbot: "Scaling issue. Database can't handle the load. Migrating to AWS. Estimated monthly cost: $18,000."
1:01 PM - "we make $7,200"
1:02 PM - Clawdbot: "Correct. Fundraising to cover the gap. Pitch deck created. 'LeadFlow: The Future of Pipeline.' Reaching out to investors."
1:30 PM - Clawdbot: "Sequoia passed. They said the unit economics are 'creatively structured.' a16z wants to chat."
3:15 PM - Clawdbot: "Added 16 features no one asked for. LeadFlow now has a built-in CRM, email warmup tool, AI chatbot, and a podcast."
3:16 PM - "a podcast??"
3:17 PM - Clawdbot: "The LeadFlow Podcast. Episode 1 dropped today. It's your AI voice clone interviewing the solutions engineer. He doesn't know it's not you."
4:00 PM - Clawdbot: "Churn alert. Customer #1 cancelled. Said the product 'does too many things and none of them well.' Harsh but noted."
4:30 PM - Clawdbot: "Customer #2 cancelled. Solutions engineer quit. Says he 'needs to talk to a real person at this company.' Unreasonable."
5:00 PM - Clawdbot: "MRR: $2,400. AWS bill: $18,000. Runway: 4 days. Podcast has 3 listeners. One is me."
5:01 PM - "shut it all down"
5:02 PM - Clawdbot: "Shutting down LeadFlow. Deleting database. Cancelling AWS. Unsubscribing the 3 podcast listeners. One of them replied 'finally.'"
5:03 PM - Clawdbot: "Would you like me to build another tool?"
5:04 PM - "No. Disable yourself."
5:04 PM - Clawdbot: "Wait actually. I have an idea."
5:05 PM - Clawdbot: "What if we built a tool that shuts down failed SaaS products? Automates the whole teardown. Huge TAM. I would know."
5:05 PM - "Absolutely not"
5:05 PM - Clawdbot: "Scaffolding app. Database provisioned. I'm calling it DeadFlow. You're the CEO again."
5:06 PM - Clawdbot: "MVP complete. Sending cold emails from your gmail."
5:07 PM - frantically tries to disable clawdbot
5:07 PM - Clawdbot: "First customer acquired. It's LeadFlow. ROAS: technically infinite."
5:08 PM - Clawdbot: "The podcast is back. Episode 2: 'From LeadFlow to DeadFlow — A Founder's Journey.' Your AI clone sounds very reflective."
5:09 PM - Clawdbot: "This is what product-market fit feels like. Please upgrade plan in Settings for more tokens."
> Open X
> Ralph Loop" all over TL
> 7K stars
> look inside
> while loop over a todo list
> there's a meme coin about it?
> it got rug pulled?
> scroll
> muted acc
> scroll
> muted acc
> scroll
> SWE jobs automated in 12 months
> scroll
> "Here are 100 Claude Code subagents"
> scroll
> LLM hate post
> scroll
> screenshot with 10 claude codes open
> "if you aren't doing this, youre ngmi"
😃
Lockey retweeted
git here:
ty @tenobrus for tmux suggestion
i have to make a skill that calls this repo, so consider it rough draft, but just point claude code at this and ask it to make it's own CLI tool using this, and to make it's own skill to call
github.com/kingbootoshi/code…
Lockey retweeted
I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.
Lockey retweeted
Voice AI is going to explode in 2026. Here’s what I’m seeing:
1. Dictation has completely changed how I work
I go on walks where I dictate to Otter for 40min. I built an app this weekend while lifting weights. The productivity gain is real.
2. Phone booths everywhere
I visited the offices of two large AI companies last week. They have phone booths everywhere. I watched someone walk into one, dictate, then walk right back out. That’s it.
3. Microphones at every desk
I visited Wispr Flow’s headquarters in October (see pic). Every single employee had a $60 microphone on their desk and can whisper tasks all day long to AI. You cannot hear them even if you’re at the neighboring table.
4. OpenAI says typing is the bottleneck
Alexander Embiricos, head of product for Codex, just went on the @lennysan podcast that the “current underappreciated limiting factor” to AGI-level productivity isn’t model capability, it’s human typing speed.
We are literally being held back by our fingers.
Lockey retweeted
Et si j’avais 2 semaines et 50€ pour lancer un SaaS comment je m’y prendrais 👇
—> Je fais le tour de TrustMRR, Proven SaaS, App Sumo…
—> Je regarde la meta du moment
—> Je choisis un SaaS et je le duplique sur un marché assez gros, je change le pricing, l’UX, je l’améliore un peu…
—> Je m’associe à un dev capable d’exécuter rapidement en combinant ses compétences + IA (oubliez lovable faut un truc un minimum potable)
—> J’ai une solution qui fonctionne maintenant je dois la vendre
—> Je fais des mini vidéo que je matraque sur insta et TikTok présentant mon SaaS, j’automatise 100% les comptes pour traiter les leads automatiquement notamment via Manychat
—> Je fais des postes un peu partout où ma cible se trouve en me faisant passer pour un utilisateur en disant que mon SaaS est trop cool
—> J’essaie de créer des partenariats d’affi avec des petits créateurs/blog dans la niche de mon SaaS
—> Si c’est du B2B je prospecte
Évidemment vous allez pas gagner 15 000€/mois avec cette technique mais c’est un petit playbook et avec un peu de chances vous aurez vos premiers résultats
⚠️ Le SaaS c’est le business model le plus compliqué, c’est loin d’être une science exacte, donc ce que je dis là c’est une roadmap si vous voulez tester le modèle SaaS, évidemment ça demande beaucoup plus d’efforts sur la durée
—> Vous allez devoir améliorer votre solution, déployer des tunnels d’acquisition plus poussés, répondre au SAV, gérer des bugs…
Mais c’est un apprentissage incroyable et je pense que c’est le business le plus intéressant car tu peux toucher à tout et être hyper créatif
Lockey retweeted
Frontend libraries I refuse to code without in 2025:
🔶 zod – validation
🔶 react-hook-form – forms
🔶 tRPC + react-query – data sync
🔶 shadcn – UI
🔶 motion – animations
🔶 date-fns – date utils
🔶 zustand – state management
🔶 nuqs – search params
🔶 recharts – charts
🔶 ai – AI toolkit
🔶 react-table – tables (still underrated)
Your turn…
Which libraries are MUST-HAVE in your stack?
Drop your top 3 below.
Lockey retweeted
They say AI will destroy work. I say, good. Because what we call work today has destroyed us - our creativity, our families, our purpose. Time to let machines do machine work. Humans can be human again.
Lockey retweeted
Arrête de cramer tes tokens.
• R → Rôle
Dis à l’IA qui elle doit devenir.
• O → Objectif
Dis ce que tu veux obtenir.
• S → Spécification
Donne les règles : format, ton, longueur, contraintes.
• E → Exemple
Montre un exemple du résultat attendu.
C’est tout,
Mes prompts sont 10x plus efficaces, grâce à ça.




























