2026-06 - W4

The Anatomy of an AI-Native Org - Ajey Gore

Chesterton’s middle finger

Writing well is hard. Writing something vaguely passable is not. By and large there are three questions to answer: “What are you changing?”, “why are you changing it?”, and “why is this a good solution?”

Ask for no, don’t ask for yes - Dan Moore!

When you have something you want to do and that you feel is in scope for your position, but you want a bit of reassurance or to let the boss know what you are up to, it’s common to reach out and ask them for permission. Don’t. Don’t ask for a yes. Instead, offer a chance to say no, but with a deadline.

Good advice. Always work, otherwise, too slow to do the “thing”. Although, not applicable for every situation, e.g. for really big projects, best to have them aligned on the priorities beforehand.

The quiet grief of adult friendship

That’s very sad, but I clearly relate to this situation, as many adults, unfortunately…

The Answer to Every Problem

Do what has to be done, when it has to be done, and do it that way every time.

An Ex-Meta L8’s Agentic Engineering Setup

How to Measure AI Investment Without Token Metrics

Measurement failures usually come back to theory failures. … Your job is not to measure everything that’s happening. What you really need to do is think about what in your organization are the key signals to measure if they give you two things. … The practical upshot for leaders: if you want to measure whether your AI investment is working, you probably should not start with token consumption or PR velocity. You should ask whether developers believe their organization treats learning as legitimate work. … On the question of what to actually do when you realize your metrics are broken, Hicks was direct. Describe how you got there. Find the argument you lost, or the organizational story that made a bad measure feel safe to commit to. Then build a change theory first, and derive the measures from that, not the other way around.

An opinionated (and mainly correct) guide to naming

Nice guide.

OpenKnowledge — Beautiful, AI-native markdown editor.

Interesting concept. Not to confuse with Open Knowledge Format from Google.

Birgitta Böckeler - State of Play: AI Coding Assistants - AI Native DevCon June 2026 - YouTube

Saying the obvious thing

When I write a technical design document at work, it’s very important to state the obvious. In fact, technical communication is so hard and general understanding is so poor that just getting people aligned on the obvious things is often enormously valuable.

On Single-Use Devices and Reading More | Matthew Bogart

I should buy one…

GitHub - dungngminh/simutil: Cross platform utility TUI app for launching iOS simulators / Android emulators, discover physical devices, ADB tools and more · GitHub

Seems really interesting tool for mobile developers.