joe

A dad, husband, fintech innovator, musician, hockey goalie, mountain biker, and photographer living in Port Moody, BC

[joe @joelo]

It’s true.

[Heather Exner-Pirot @ExnerPirot]

The fact Canada responded to the external crisis foisted upon us, not with polarization and upheaval but with centrist, reasonable governments across the board, is pretty great.

Manitoba is now the most left wing and Alberta is the most right wing and they both lean into the centre more than the extremes on policy preferences (this will be even more true now that we are post-referendum, where the Alberta electorate clearly expressed a preference for centrism).

[joe @joelo]

@Astro_Kutryk Hi from Port Moody BC!

[joe @joelo]

@thdxr OpenCode Goey McGoFace

[joe @joelo]

@thdxr @paulg I love it. Thanks!! I recommend it to everyone.

[joe @joelo]

@gdb Agreed! Humans want to talk to humans.

[Xinyu Zhou @zxytim]

Will do

[Ahmad @TheAhmadOsman]

https://t.co/riIctxjHoN

[antirez @antirez]

I want to say a final thing about my Fable first reaction: I dedicated my life to programming and I'll use every innovation in the field, also to extract value and bring it to the local inference world, to Redis, and so forth. But:

[joe @joelo]

@DennisCW_ And a fsd transfer

[Google AI @GoogleAI]

Today, we’re launching Gemma 4, our most intelligent open models to date. Built with the same breakthrough technology as Gemini 3, Gemma 4 brings advanced reasoning to your personal hardware and devices.

Here’s what Gemma 4 unlocks for developers:

— Intelligence-per-parameter: Our 31B (Dense) and 26B (MoE) models deliver state-of-the-art performance for their size, outcompeting models 20x their size on @arena

— Commercial flexibility: Released under a permissive Apache 2.0 license for complete developer flexibility and digital sovereignty

— Agentic workflows: Native support for function-calling and structured JSON output allows you to build reliable, autonomous agents

— Multimodal edge AI: The E2B and E4B models bring native vision, audio, and low latency to mobile and IoT devices

— Long-context reasoning: Up to 256K context windows allow you to process entire repositories or large documents in a single prompt

Whether you're building global applications in 140+ languages or local-first AI code assistants, Gemma 4 is built to be your foundation. Explore in @GoogleAIStudio or download the weights on @HuggingFace, @Kaggle, and @Ollama.

[joe @joelo]

The MacBook neo is what I always wanted my iPad to be. Love it!!

[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.

[joe @joelo]

@OpenAI We want this

[dominik kundel @dkundel]

We just published a new AI-Native Engineering Team guide based on what engineering teams are asking for as they adopt Codex and the new GPT-5.1-Codex-Max model.

It covers:
🧩 How coding agents fit into each phase of dev across planning, design, maintain
🧰 Practical checklists and setup patterns you can use right away
📈 How to introduce agents into an org and scale as teams build trust

Read the guide 👉 https://t.co/yyM3aIF2Vo

[joe @joelo]

It’s true - the world runs on Excel and will forever.

[Trung Phan @TrungTPhan]

Satya Nadella on why Microsoft Excel has been so durable after 40 years:

> the power of lists and tables
> the malleability of the software (“a blinking canvas”)
> spreadsheet software is Turing complete (“I can make it do everything”)
> it’s the world’s most approachable programming environment (“you get into it without even thinking your programming”)

[joe @joelo]

@ajassy @OpenAI Will OpenAPI’s services be available on bedrock eventually?

[joe @joelo]

@leepace It’s extraordinary.

[OpenAI Newsroom @OpenAINewsroom]

These “OpenAI tokens” are not OpenAI equity. We did not partner with Robinhood, were not involved in this, and do not endorse it.  Any transfer of OpenAI equity requires our approval—we did not approve any transfer.

Please be careful.

[joe @joelo]

@AravSrinivas Link phone number to pro account?

[joe @joelo]

@sundarpichai Incredible! Just amazing what @Google is doing for computing, AI, and really, everyone.