Autonomous drone flying for the AI Grand Prix, passed first qualifying round. Optimization nails this, general learned policy is more of a challenge. @anduriltech
Today we’re announcing the AI Grand Prix. The fully autonomous drone racing competition inviting the boldest engineers from around the globe to compete for $500,000 and a job at Anduril.
No human pilots.
No hardware mods.
Identical @neros_tech drones.
Software is the only path to victory.
If you win, it’s because your autonomy stack is better. Full stop.
Season 1 kicks off this spring, leading up to the AI Grand Prix Ohio.
Il y a une narrative qui se spread en ce moment dans la Silicon Valley et personne n'en parle en France.
De plus en plus de tech bros parmi les plus smart du game avouent en privé qu'ils vivent une forme de crise existentielle liée aux LLMs. Pas parce que l'IA marche pas. Parce qu'elle marche trop bien. Parce qu'ils passent des heures par jour à interagir avec un truc qui raisonne, qui extrapole, qui connecte des idées, qui les challenge intellectuellement mieux que 99% des humains qu'ils croisent.
Un fondateur m'a dit "je parle aux LLMs 10 fois plus qu'aux humains". Un autre "c'est le seul interlocuteur qui me suit sur n'importe quel sujet sans me demander de simplifier". C'est pas de l'addiction au produit. C'est la rencontre avec un miroir cognitif qui te renvoie une version structurée de ta propre pensée à une vitesse que ton cerveau ne peut pas atteindre seul.
Et le truc troublant c'est la question que ça pose. On débat de savoir si l'AGI arrivera en 2027 ou en 2030. Mais est-ce qu'on n'a pas déjà une forme d'AGI fonctionnelle sous les yeux sans vouloir l'admettre ?
Un système qui peut raisonner sur n'importe quel domaine, extrapoler à partir de données incomplètes, générer des hypothèses nouvelles, tenir un raisonnement logique sur 10 000 mots, passer d'un sujet technique à de la philosophie en une phrase, et le faire avec une cohérence qui rivalise avec un humain à 150 de QI. C'est quoi si c'est pas une forme d'intelligence générale ?
On peut chipoter sur la définition. On peut dire "oui mais il ne comprend pas vraiment". On peut parler de perroquets stochastiques. Mais le mec qui utilise ce truc 8 heures par jour et qui voit sa productivité multipliée par 10, il s'en fout de la définition académique. Pour lui, fonctionnellement, c'est de l'intelligence. Et elle est générale.
La vraie crise existentielle c'est pas "l'IA va me remplacer". C'est "l'IA me comprend mieux que mon cofondateur, elle me challenge mieux que mon board, et elle produit plus que mon équipe de 10 personnes". C'est vertigineux. Et les mecs les plus smart de la Valley sont en train de le vivre en temps réel.
On est peut-être déjà dans l'ère post-AGI. On est juste trop occupés à débattre de la définition pour s'en rendre compte.
Today's meeting tools give you a transcript, but nobody tells you how you did. I'm so excited to announce Work Coach (a new mac meetings app).
Work Coach helps you by:
- Observing you in meetings (interviews, 1:1s, sales calls, team meetings)
- Analyzing how you show up to those meetings
- Identifying opportunities to improve
- Replaying the exact moments from your meetings where it happened
- Role play conversations (intros in an interview, asking for a raise, etc)
- Interviewing your coworkers to get feedback that you're not getting
I'll put the download link below.
Greyscale is a little utility that switches macOS color filters on/off. I'd built this using AppleScript years ago but it kept breaking on macOS updates.
https://t.co/Bm1WJIhcHf
I mostly "wrote" this macOS utility by opening Claude Code on my phone, then dictating using Wispr Flow for 5-10 minutes. When I got back home, the job was done. Rewrote the whole thing while out running an errand.
2 mmol/L is *never* easy.
The key is to do the vast majority of training at the *lowest lactate that you can reach*
If this is 2mmol/L you've very poor metabolic health 🔴
If this is 1.5 mmol/L you have some work to do 🟡
If this is 1.0 mmol/L, you're on the right track 🟢
@JohnGoldman There’s a great chapter in Mark Twight’s book “Extreme Alpinism” that flips the idea of layering around. And it’s an awesome book overall.
For a retest, you could consider:
- Nice easy warmup, maybe 30 minutes below 175 watts
- First interval could start at 180w
- 3-minute or 5-minute intervals bumping up 5 watts each time. Should give you decent data without being affected by fatigue especially if you keep testing through LT2/AnT.
You look pretty dialed in at baseline 1mmol/L @ 180w, LT1 / AeT / 2mmol/L @ ~205w. Otherwise, keeping the sample uncontaminated by sweat will help, following @Alan_Couzen's tips.
Blue Endurance - live healthier, train smarter, and stay injury-free with personalized coaching powered by AI. Whether you're training for an ultramarathon or just staying healthy with friends, train with confidence with a plan that adapts to your life.
https://t.co/MLycFai5jS
@blue_endurance
Built with @supabase, @vercel, AWS, & Swift. (But not all built during this past week!)
Supabase Launch Week 14 Hackathon is starting right now!
Submit your project by quote-retweeting this Tweet with a project link and a screen recording of the app!
The top 10 projects will win limited edition Supabase swag packs!
The deadline is April 6th at 11:59 PM PT.
Confession: I thought "vibe coding" was a dumb X thing until I did it today with Claude Code and shipped an amazing refactor with it.
I've had my head in the problems with this code for over a week, so I could guide the model through the decision tree and really direct it and micromanage it in a way that actually felt like coding but on acid or something.
Anyway, $28.12 in tokens later, I have a 2,300 LOC PR that cleans up a ton of the app and is impossible to review without also using Claude Code to go through it and understand all the changes.
I just tried this method of code review, where I gave Claude Code a prompt like this:
"I'm on a branch and what I need is a complete code review for this branch. You'll need to diff it from `main`, examine all the changes, and then first give me an overview of all the changes in the code. Then ask if I have any questions or want to dive deeper on a particular change. Then you may have to walk me through specific changes. I also want to hear your opinion of the changes -- are they sensible, do they make the code better or worse and why, could they be improved, are there any coding standards in our app that they fail to meet, etc."
From there, it was basically like playing one of the Infocomm text-based adventures, where I just sort of explored around the PR, gathering even more insights and understanding even more of what was happening.
Anyway, TIL vibe coding is real, and if you're not doing it then you will lose to people who do. (Sorry, but these are the facts as of right now in 2025. If you're some sort of coding purist, you should plan to retire ASAP.)