Evan
1.3K posts





SemiAnalysis’s Head of Data Center and Energy Infrastructure Research: “Anthropic, we estimate, had 1.5 gigawatts of capacity at the end of 2025. By 2027, they’re going to have 10, so that’s 9 gigawatts in two years. That’s essentially the size of Google today, and you have four companies trying to do that within the same timeframe.”

In the dating app+IG era, very few couples in major U.S. cities (excluding couples who met in college) are ones where the girl is 2+ points more attractive than the guy. Vast majority, guys are more attractive than the girl. Olivia Rodrigo's new BF is an example of this.




This is the main reason why there is only one significant math problem that got solved via Fable





Professor Babai emailed me back, oh my god I'm scared I really hope I'm not wasting his time 😭 Can someone please have Fable do an adversarial review ASAP?





Megacaps used to demand high earnings multiples because they were asset light businesses that had moats they didn’t have to spend on This has changed in the last 2 years as these companies need to put hundreds of billions into building data centers to keep a competitive edge





@P_Remarks I feel like this is the only account consistently posting long stonks at 52w lows. Just an observation

I think I finally figured out how to use AI at scale of course, the fact Fable is good is part of it. but I also changed how I work, and it all comes down to one key realization: you don't need to audit the code, but you NEED to audit the *choices* it made. if you just do that, things will work out, and you'll never lose a codebase to chaos. with Fable at least, the following seems to hold: if I give it a good decision: Fable implements it PERFECTLY if I let it decide instead: Fable may make some bad choices that's how I see Fable: as a perfect execution machine capable of converting good decisions into good codebases, no matter how large. given a concrete plan, it lands its implementation. but when anything is underspecified, it can, and will, make bad choices. that's what you must audit. "while working on this, which choices did you make that you're not confident of? list all." then, you just review that. not the git diff, not 1000's of lines of code. just the choices it made along the way. below is a fresh example. overnight, I asked Fable to fix an issue related to MatMul parallelizing worse than expected. it tracked the culprit with perfection, and landed a solution that DID work. but the solution was not general. it just doubled a buffer, which coincidently fixed the program at hands, but the underlying issue was still present. when it completed the job, it declared success. if I just merged it blindly, the issue would still be dormant. that's the main mistake one can do with AI. instead, I asked it to spell out all decisions it made, spotted the bad one, corrected its course, and now the codebase is clean, correct and the issue is gone for good I really think that if you do that religiously - i.e., NEVER merge without this "which decisions you made?" audit - you can go VERY far without ever reading a single line of code. at least on Bend, this is working incredibly well. despite heavy use of AI to implement an ungodly amount of features I could never dream of, the codebase is still in a superb state, with no signs of degradation fresh example below ↓









