floetic

@Sandeman52 He’s transparent and posts screenshots of his trades that succeed and failed… do you or do you just claim your positions and wins?

You know what’s crazy? This dude Kevin Xu Has 3x more followers than me. I have 4 mill more than him and a CAGR way above his. He charges 200 per month for his “ideas” I charge nothing. Yet I’m way below his follower count. Bro, why are you charging that much if you have that much? What am I missing?

@chamath You need github.com/garrytan/gbrain cc @garrytan

This may be a dumb question but I’ll ask it here anyways: I can’t find a good way for my various AI chats to automatically sync its conversation history into a structured knowledge base. So that as I update various chats from time to time and refine context, my knowledge base automatically grows with this new info.

@bcherny @NATE9169 Me :)

@NATE9169 dm me your address? will mail a swag gift box

See everyone tomorrow!!

LFG RAPTORS! #WeTheNorth

Chuck is right… if Scottie Barnes played on an American team he would be rated top 15 in the league. Evan Mobley is nowhere near Scottie Barnes… #WeTheNorth

This is still Masai's team... don't forget. #WeTheNorth

Pre-ordered! @markpinc

Palantir CTO @ssankar on what he would tell his children to focus on in the age of AI: "Agency. Extreme agency." "All the other skills, you'll be able to figure out as you go."

AI is a shortcut. So it’s useful. But it’s lazy. So it speeds execution. But it hides complexity. So you want to use it. But definitely not overuse it. So the user of AI often loves it. But the reader of AI often hates it.

My 3.5-hour conversation with @naval. Fresh takes on every idea from The Almanack of Naval: happiness, judgment, knowledge, leverage. Now in one episode, available on Spotify, Youtube, etc.

🇨🇦 Engineers behind AI were educated in Ontario OpenAI: Co-Founder Ilya Sutskever (UofT) xAI: Co-founders Elon Musk (Queen's), Zhang Guodong (UofT) and Zihang Dai (UofT) In 10 years we'll all agree failing to attract them to build in Ontario is our biggest policy failure ever.

@brian_armstrong @grok what should I do now? :)

Druck is right. Saddle up.

Software development is undergoing a renaissance in front of our eyes. If you haven't used the tools recently, you likely are underestimating what you're missing. Since December, there's been a step function improvement in what tools like Codex can do. Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging. Not everyone has yet made that leap, but it's usually because of factors besides the capability of the model. Every company faces the same opportunity now, and navigating it well — just like with cloud computing or the Internet — requires careful thought. This post shares how OpenAI is currently approaching retooling our teams towards agentic software development. We're still learning and iterating, but here's how we're thinking about it right now: As a first step, by March 31st, we're aiming that: (1) For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal. (2) The default way humans utilize agents is explicitly evaluated as safe, but also productive enough that most workflows do not need additional permissions. In order to get there, here's what we recommended to the team a few weeks ago: 1. Take the time to try out the tools. The tools do sell themselves — many people have had amazing experiences with 5.2 in Codex, after having churned from codex web a few months ago. But many people are also so busy they haven't had a chance to try Codex yet or got stuck thinking "is there any way it could do X" rather than just trying. - Designate an "agents captain" for your team — the primary person responsible for thinking about how agents can be brought into the teams' workflow. - Share experiences or questions in a few designated internal channels - Take a day for a company-wide Codex hackathon 2. Create skills and AGENTS[.md]. - Create and maintain an AGENTS[.md] for any project you work on; update the AGENTS[.md] whenever the agent does something wrong or struggles with a task. - Write skills for anything that you get Codex to do, and commit it to the skills directory in a shared repository 3. Inventory and make accessible any internal tools. - Maintain a list of tools that your team relies on, and make sure someone takes point on making it agent-accessible (such as via a CLI or MCP server). 4. Structure codebases to be agent-first. With the models changing so fast, this is still somewhat untrodden ground, and will require some exploration. - Write tests which are quick to run, and create high-quality interfaces between components. 5. Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high - Ensure that some human is accountable for any code that gets merged. As a code reviewer, maintain at least the same bar as you would for human-written code, and make sure the author understands what they're submitting. 6. Work on basic infra. There's a lot of room for everyone to build basic infrastructure, which can be guided by internal user feedback. The core tools are getting a lot better and more usable, but there's a lot of infrastructure that currently go around the tools, such as observability, tracking not just the committed code but the agent trajectories that led to them, and central management of the tools that agents are able to use. Overall, adopting tools like Codex is not just a technical but also a deep cultural change, with a lot of downstream implications to figure out. We encourage every manager to drive this with their team, and to think through other action items — for example, per item 5 above, what else can prevent a lot of "functionally-correct but poorly-maintainable code" from creeping into codebases.

VC vs. founder

@Klein25 lol

- The Blue Jays thought they signed Shohei Ohtani. Dodgers won. - The Blue Jays prioritized signing Roki Sasaki. The Dodgers won. - The Blue Jays thought they won the 2025 World Series. The Dodgers won. - The Blue Jays thought they signed Kyle Tucker. The Dodgers won again. Brutal

@Dodgers congrats! @DodgersNation @BlueJays #WantItAll

If you are the founder of a highly valued illiquid startup, set some time aside and read this entire article. The act is designed to bankrupt you and to personally punish any appraiser or accountant who disagrees.

In San Francisco you can shove an Asian senior citizen to his death, laugh and photograph it, and the jury will not find you guilty of murder. This is where decades of progressive policy has brought us.

If you have kids, this will hit hard. You’ve been warned 😭

@garrytan @martin_casado Ro Khanna is up for re-election in the 2026 midterm elections. Let’s do it.

@martin_casado Time to primary him

Ro has done a speed run alienating every moderate I know who has supported him. Including myself. Beyond being totally out of touch with that faction of his base, he’s devolved into an obnoxious jerk. At least that makes voting him the fuck out all the more gratifying.