Sakana AI CEO David Ha @hardmaru:
"If you assemble a team of Avengers, that team will be better than the individual heroes. The same with AI."
Sakana Fugu, their new AI “model” goes toe-to-toe with Mythos and Fable 5 on a few benchmarks — without training a single frontier model of its own.
Fugu orchestrates between different frontier AI models to achieve higher results.
On the real risk, David adds: "I'm more concerned about the structure of dependency… you don't want to be tied to a single particular AI model or a single particular vendor."
An exclusive 1:1 with CROSS DIG’s @mshrnakagawa
#SakanaAI #SakanaFugu
I stumbled upon this timely article many years ago. Been thinking about it in the context of one's career, especially in AI, and how to stand tall in a sea of noise
https://t.co/GRBrbR23SW
🚨Kylian Mbappé was asked who the greatest footballer in history is between Cristiano Ronaldo and Lionel Messi:
🎙️ Reporter: “Kylian, when people debate the greatest player of all time, where do you stand?”
🗣️ [Smiles] “I always try to avoid these questions because, honestly, we are talking about two players who changed football forever.
“I have huge respect for both Cristiano Ronaldo and Lionel Messi. They have dominated the game for nearly two decades and achieved things that many people thought were impossible.
“But if I have to choose one, I would say Cristiano Ronaldo.
“It’s not only about the trophies, the goals or the records — it’s about the journey.
“He succeeded in different leagues, different countries and different teams. He won everywhere he went and adapted to every challenge.
“What has always inspired me most is his mentality. His discipline, his work ethic and his desire to improve every single day are unmatched.
“He showed the world that talent is important, but mentality and hard work can take you even further.
“For young players, Cristiano proved that there are no limits if you are willing to sacrifice and push yourself every day.
“That is why, for me, he is the greatest.
#ARGAUT
{@talksport}
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.
It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.
I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.
I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.
Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
New post: why and how @linear is moving to @stylexjs.
Codemods and agents are doing the heavy lifting. Humans still have to perform detective work on cursed hover states.
https://t.co/lSnDvJwTvL
👨🎨 We're sharing a formula for making vibe-coded apps look professional.
It's a deconstruction of the "science of design" and we think it will help you coach your agents into mobile app design that brings polish to your apps.
The formula and examples are in the post below ↓
Erling Haaland was asked about Norway’s Group I decider against Kylian Mbappe’s France.
“I don't care much. They'll probably beat us and win the title.” 😂
6 yr ML PhD, trained Olmo 3, trained Nemotron 3, but still forced to grind Leetcode and Neetcode 75.
Despite all the headlines saying otherwise, Leetcode is clearly not dead.
Somehow knowing dynamic programming is more important than knowing data parallelism for interviews.
I'm joining OpenAI next week!🥹 The job search turned out to be really challenging but also super rewarding, so I wrote a small blog to share what I learned along the way and hopefully make the process a little less mysterious for the next person. https://t.co/6FigSBdenD
It’s incredible that /make-interfaces-feel-better has already been installed more than 30,000 times.
It contains a lot of tips that make interfaces feel better, across UI, animations, performance and more.
npx skills add jakubkrehel/make-interfaces-feel-better
this took so long for me to understand: the bottleneck to more innovation is not more high intelligence people, but more people having an interest in hard problems
it's impossible to create new useful things if you don't get immense happiness from making that thing
If you're on your way to building a billion dollar company that involves a web app, here are some of my notes on architecting the frontend.
if you don't do this, it's probably fine but one day you'll hire someone to fix it but truly that person could be doing some other higher value thing if you make some key optimizations on day 1
you don't even have to learn anything you're gonna tell your agents to do it anyways!
okay here it goes:
- Make your server code generate a openapi spec which then generates all the relevant client side code. Never do this by hand. Typing backend types instead of generating them should be banned
- You need to make a decision on how the client talks to the backend. rest/graphql works in which case please just use tanstack query. other libraries will look similar but tanstack query truly is goated.
- if you want linear style sync setups or offline mode, think about this HARD and architect it from day 1. Bolting this on later is so tedious.
- People like using plain react router but things have gotten a lot better since then. Try their new framework mode or just even use tanstack router. Use route data loaders.
- If you store a lot of state in query params, make that a first class citizen and make sure its type safe. use nuqs or tanstack query.
- Most apps just need a single state management situation for server state and thats it. If you have other bespoke needs, i have quite like zustand and xstate/store.
- If you have a super interactive app where things come in and out of view, theres a lot of frontend state to maintain, music is playing and what not, lock in and learn xstate. Trust me if you wanna keep ur sanity, you need to model ur frontend as a state machine otherwise you're gonna be deep in useEffect hell
- React compiler is here my friends, the days of useMemo and useCallback are gone. Update your priors accordingly
- Tailwind is easy and fun but makes it really hard to maintain a large app with consistent styling. You need a "agent-first design system/component library" but maybe this is a rant for another day
- Don't be afraid to hack your routing library to fit your needs more closely. A lot of apps have "drawers" to show additional info. You should 100% be able to say "here's a route, make it a drawer" and everything should be handled from there.
- Managing loading and error states using isPending and isError is madness. Lean into Suspense and ErrorBoundary.
- Figuring out a blessed path for websockets and SSE on day 1 i think will pay dividends in the long term if you're building anything AI related.
- If you're building a SPA, don't use next.js. it literally makes no sense. Why would you do this.
- Definitely deploy on Cloudflare or vercel. There are other services but trust, there have weird missing features.
- Assuming you build something people want, the next job is to build the factory so it can efficiently build the thing. Act accordingly.