Elmer Morales

Out here at #CES2025 launching something new. Who’s ready to see what we’ve been cooking? #aiagents

RT @soraofficialapp: We’re saying goodbye to Sora. To everyone who created with Sora, shared it, and built community around it: thank you.…

was messing with the OpenAI base URL in Cursor and caught this accounts/anysphere/models/kimi-k2p5-rl-0317-s515-fast so composer 2 is just Kimi K2.5 with RL at least rename the model ID

A “computer” used to be a job title. Then a computer became a thing humans used. Now a computer is becoming a thing computers use.

Cybertruck is way more awesome than people realize

If there’s something you want to create but you get demotivated when you find out a famous/impressive person is doing it too, I highly recommend you fight that feeling. I’ve seen too many instances of nothing getting shipped by said person a year later.

People giving OpenClaw root access to their entire life

@ohryansbelt @garrytan LMAO 🤣

@garrytan You coded a blog Garry

About 1/3 of the top technical CEOs are completely AGI pilled by coding again. I am one of them. Highly recommend. Totally exhilarating to be back shipping new products and software again

You can skip all the parties, all the conferences, all the press, all the tweets. Build a great product and get users and win.

The most impressive people I know spent their time with their head down getting shit done for a long, long time.

@ibab Agree 1000%.

What’s the best open alternative to OpenClaw right now? Doesn’t make sense to put all your data into it if it’s owned by OpenAI.

America has 18 million zombies…

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.

This is a critical aspect of the Billionaire Tax Act. It makes founder-led companies practically illegal. If a founder-CEO of a $1B private company owns 3% but keeps 100% of the voting power, he gets taxed on the value of the whole company. $50M tax bill for $30M net worth.

We have frozen all child care payments to the state of Minnesota. You have probably read the serious allegations that the state of Minnesota has funneled millions of taxpayer dollars to fraudulent daycares across Minnesota over the past decade. Today we have taken three actions against the blatant fraud that appears to be rampant in Minnesota and across the country: 1. I have activated our defend the spend system for all ACF payments. Starting today, all ACF payments across America will require a justification and a receipt or photo evidence before we send money to a state. 2. Alex Adams and I have identified the individuals in @nickshirleyy's excellent work. I have demanded from @GovTimWalz a comprehensive audit of these centers. This includes attendance records, licenses, complaints, investigations, and inspections. 3. We have launched a dedicated fraud-reporting hotline and email address at childcare.gov Whether you are a parent, provider, or member of the general public, we want to hear from you. We have turned off the money spigot and we are finding the fraud. @ACFHHS @HHSGov

@pelaseyed That’s kinda weird.

@TechBinary99 @MKBHD LMAO 🤣

@MKBHD Better not be another app for wallpapers !

Friday. Dropping the best video I've ever uploaded. Can't wait 👀

The future is going to be AMAZING with AI and robots enabling sustainable ABUNDANCE for all!

Amazon’s SVP of AI in Sources today: “None of these benchmarks are real… The only way to do real benchmarking is if everyone conforms to the same training data and the evals are completely held out…. The evals are frankly getting noisy” sources.news/p/amazons-anti…