Tao

@ericzakariasson would love to have "format on save" in the editor window work in the agent window if possible 😶

how can we make cursor 3 better? send us any bugs, feature requests, or feedback you have!

Neuroscientist Reveals Why You Must Go EXTREME to Win Big:

Poker will never die, here is why: The vast majority of poker players are slightly losing, often thinking they are winning players, victims of the Dunning-Kruger effect. They see Linus making a controversial play and call it spew without any proof, just because they think they are right. They make a bad play, blame it on someone else or on variance, and stay in that belief, thinking they are right and everyone else is wrong. Everyone falls victim to the Dunning-Kruger effect at least once in their life, believing they are much better than they actually are. Everyone can break out of that cycle though: ask yourself constantly what you could have done better, put your ego aside, and learn from better players with an open mind. This is why poker will never die: many never break that pattern and stick to their beliefs. You made mistakes, you will keep making many mistakes in your life. But the key is to acknowledge your mistakes, learn from them, and do better next time. Everyone is struggling with that. I used to struggle a lot with that and still am. Getting better every day ❤️

You want to crush poker this year? Here’s how you do it: 1/10 Build a strong theoretical understanding: It helps you develop a deep understanding of the game, identify mistakes, exploit your opponents, grasp essential concepts, and stand your ground against strong players.

@padspoker @DanielSternald sik

Announce @DanielSternald 🕺🕺

“Get the fucking money”

Biggest score of my poker carrer🤩Been awhile since i posted recent MTT results, but this one was surely worth waiting for🥳Record breaking stream: Peaked at 3.9k viewers on twitch, and 2.3k on youtube📈 Thank you so much guys for all the amazing support in the stream, we had an epic moment♥️ @GGPoker @_pokercode

This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.

I vibecoded an open-source poker river solver over the holiday break. The code is 100% written by Codex, and I also made a version with Claude Code to compare. Overall these tools allowed me to iterate much faster in a domain I know well. But I also felt I couldn't fully trust them. They'd make mistakes and encounter bugs, but rather than acknowledging it they'd often think it wasn't a big deal or, on occasion, just straight up try to gaslight me into thinking nothing is wrong. In one memorable debugging session with Claude Code I asked it, as a sanity check, what the expected value would be of an "always fold" strategy when the player has $100 in the pot. It told me that according to its algorithm, the EV was -$93. When I pointed out how strange that was, hoping it would realize on its own that there's a bug, it reassured me that $93 was close to $100 so it was probably fine. (Once I prompted it to specifically consider blockers as a potential issue, it acknowledged that the algorithm indeed wasn't accounting for them properly.) Codex was not much better on this, and ran into its own set of (interestingly) distinct bugs and algorithmic mistakes that I had to carefully work through. Fortunately, I was able to work through these because I'm an expert on poker solvers, but I don't think there are many other people that could have succeeded at making this solver by using AI coding tools. The most frustrating experience was making a GUI. After a dozen back-and-forths, neither Codex nor Claude Code were able to make the frontend I requested, though Claude Code's was at least prettier. I'm inexperienced at frontend, so perhaps what I was asking for simply wasn't possible, but if that was the case then I wish they would have *told* me it was difficult or impossible instead of repeatedly making broken implementations or things I didn't request. It highlighted to me how there's still a big difference between working with a human teammate and working with an AI. After the initial implementations were complete and debugged, I asked Codex and Claude Code to create optimized C++ versions. On this, Codex did surprisingly well. Its C++ version was 6x faster than Claude Code's (even after multiple iterations of prompting for further optimizations). Codex's optimizations still weren't as good as what I could make, but then again I spent 6 years of PhD making poker bots. Overall, I thought Codex did an impressive job on this. My final request was asking the AIs if they could come up with novel algorithms that could solve NLTH rivers even faster. Neither succeeded at this, which was not surprising. LLMs are getting better quickly, but developing novel algorithms for this sort of thing is a months-long research project for a human expert. LLMs aren't at that level yet.

I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit. My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently. So, here goes.

I'm not joking and this isn't funny. We have been trying to build distributed agent orchestrators at Google since last year. There are various options, not everyone is aligned... I gave Claude Code a description of the problem, it generated what we built last year in an hour.

The single biggest shortcoming with all MTT GTO solvers is that they don't account for bust-outs on other tables. Consider the Main Event bubble. There are ~1,500 players active. The chance of someone busting during this specific hand is high. However, solvers completely ignore this background churn. They assume stacks at every other table are "frozen in place" for the purpose of the ICM calculation. And no, Future Game Simulation (FGS) doesn't fix this. In practice, FGS just simulates future push/fold scenarios on the active table. FGS doesn't account for play on other tables. What does this mean for tournament pros? It means modern solvers drastically underestimate the EV of folding in large fields when pay jumps matter.

Population collapse continues to accelerate

@tim_cook 🙏

Heartbroken by the devastating fire in Hong Kong. Everyone affected is in our thoughts and we are thankful for the first responders. Apple is donating to relief efforts on the ground.

Behold: the reality of our relativity in the solar system.

@jaredpalmer @MelkeyDev @github i legit thought its my internet as well....

@MelkeyDev @github Heard. I'll be able to share an update soon on the gameplan and some of the new architecture changes that are in the works. Site performance is now a top priority.

Did GutHub engineers just stop working on the platform? Everything feels SO SLOW. To the point where I thought I was having internet issues. But adding comments on reviews is taking forever. What's going on @github ?