Frosty

@chelseafc | Fan account

[𝑻𝑯𝑬 𝑮𝑬𝑵𝑬𝑹𝑨𝑳 𝑺𝑵𝑶𝑾 🇨🇮 @GeneralSnow_]

It will cost you 0 Naira to Retweet this post.

[Abdul-Aziz Na'ibi Abubakar @jrnaib2]

Repost Aggressively.

[Ọládélé 🇳🇬👑 @Theoladeledada]

It cost $0.00 to retweet this

[Frosty @CFCfrost]

@HEALTH__LIVING @InterestingSTEM @grok is the information in the video correct?

[Instablog9ja @instablog9ja]

As a woman, if you enter marriage thinking only about p%verty alleviation, you’ll fail. Financial intelligence separates wife material from non-wife material — Man says as he shares his thoughts on home finances

[DAN KOE @thedankoe]

https://t.co/7l7Jef99QZ

[Greg Brockman @gdb]

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.

[Zara Zhang @zarazhangrui]

Add this paragraph to the https://t.co/CGO09Sihd0 file to turn Claude Code into Claude Teacher. Every project is a lesson to become more technical.

"For every project, write a detailed FOR[yourname].md file that explains the whole project in plain language.

Explain the technical architecture, the structure of the codebase and how the various parts are connected, the technologies used, why we made these technical decisions, and lessons I can learn from it (this should include the bugs we ran into and how we fixed them, potential pitfalls and how to avoid them in the future, new technologies used, how good engineers think and work, best practices, etc).

It should be very engaging to read; don't make it sound like boring technical documentation/textbook. Where appropriate, use analogies and anecdotes to make it more understandable and memorable."

[nick vasilescu @nickvasiles]

Clawd Bot is a 24/7 assistant with access to its own computer.

What if there were ten,
or a hundred,
or a thousand??

all running 24/7 in the cloud with access to your files, your Gmail, calendar, everything about you...

That's the future, and we're living it today.

[The Startup Ideas Podcast (SIP) 🧃 @startupideaspod]

How to set up Claude code in 2 min (for complete beginners)

You need 3 tools to change your business.

1) Claude code builds
2) GitHub stores
3) Vercel hosts

Costs $20.

What a time!

Thank you @boringmarketer

[𝐀𝐬𝐚𝐤𝐲𝐆𝐑𝐍 @AsakyGRN]

“Don’t come to the Super Eagles if you’re not ready to give everything for the nation. If the NFF delays your payment, let it go. Social media has distracted you all, and the praise got to your heads. When Argentina were preparing to play us four days before, none of their players were active on social media.”

— Bovi bl asts Super Eagles.

[Framer University @learnframer]

the website that instantly made all designers feel like CRAP...

[Frosty @CFCfrost]

@businessbarista Claude

[Frosty @CFCfrost]

@AdewaleYusuf_ US

[Toluwani @Toluwaniodukoya]

ONLINE SANTA IS BACK!

It’s that time again to spread love and joy!
What do you need this season?
Simply drop it in the comments
or share your account details
and let’s see what God will do.

Merry Christmas! 🎁❤️

[Mod @CFCMods]

This guy is a top 3 player in the world as a right back and also as a midfielder, I’ve never seen anything like it before.

[U.S. Mission Nigeria @USinNigeria]

U.S. company @Google is democratizing access to technology to help young people in Africa dive deeper into the innovation sweeping across the continent. Between October 7 and December 9, 2025, university students in Nigeria (aged 18 and above) can subscribe to 12 months of free access to the Google AI Pro plan.
Visit https://t.co/urMKhcuQ8z to create an account.

Learn more: https://t.co/NSi8yqQtps

[Google Antigravity @antigravity]

Meet Google Antigravity, your new agentic development platform.

An evolution of the IDE, it's built to help you:
- Orchestrate agents operating at a higher, task-oriented level
- Run parallel tasks with agents across workspaces
- Build anything with Gemini 3 Pro.

[Robert Morrison @RobertAnim8er]

“Why do games take so long to make?”

Games:

[Gunther Eagleman™ @GuntherEagleman]

Cancel Netflix