Fable unlocks a world where everyone can automate agents in their own way x.com/i/article/2095…

128GB of unified RAM just arrived. I’ve never had a machine even close to being this powerful.

Which model should I load up first?

I’ll report back with performance.

Deepseek 4.1 Flash feels like Opus. It's not as smart, but its so, so close.

I expect they will close this gap in the next 3 months.

The progress from Deepseek is just astounding.

How I use AI to make videos that don't look like they were made with AI. x.com/i/article/2107…

Saw this on my way into the office in SF this morning and it was just so encouraging so I wanted to share the light.

Going to @github Universe?

Join myself, @pierceboggan, @Jujujuliakasper, @okatiesavage and @JamesMontemagno for a look at how your team can work seamlessly with @github Copilot...pretty much everywhere.

reg.githubuniverse.com/flow/github/un…

Left handed cursor pointer ...

Interesting to anyone? Small but delightful inclusion?

Every coding agent best practice is a guess until you measure it. So today we launched the Developer Agent Experience (DevAX) site, about what coding agents do when developers ask them to build with your technology.

Developers judge your technology by what their agent builds with it, and a newer model won't necessarily fix that. On architecture work, a newer model finished as many tasks as the one before it. It did them at lower quality and used 12 times the tokens at the median. You only find that out by measuring.

The site has the AX Practitioner Playbook, from your first baseline to measuring whether a fix improved quality and what it cost per task. You can also install it as a skill and ask your agent: npx skills add microsoft/scope/docs/ax-playbook/ax-practitioner

aka.ms/agent-experien…

I've managed fully remote engineering teams for ~7 years, from small teams to rapidly growing orgs spanning 10+ countries.

I've developed some pretty strong opinions about what makes remote work actually work:

<rant>

1. YOU MUST GET "THE TEAM" TOGETHER ONCE A QUARTER, NO EXCEPTIONS. The faster the team/company is growing, the more critical this is. If you follow no other piece of advice follow this one. Remote work is built on a foundation of trust which for most humans can only be built in person. Think about a person you know well who has extremely dry humor. Would you be able to detect that characteristic if you met them for the first time over SMS or slack? Bonds are built over dinner, a beer, an in person hackathon. And those bonds carry forward to the rest of the time spent remote. **for some definition of "the team" - can be a mix of immediate team, org, company-wide, all are useful at different cadences.

2. Managers must be pros and must be highly technical. Many non-technical managers rely on lazy half-ass signals like "who left the office last". As a remote manager you literally have no option other than to inspect the concrete outputs to understand what is going on. This tip is also very useful to non-remote teams 🙂

3. No juniors except for exception cases. Exceptional cases are obviously exceptional. Gotta build the muscle before you play on hard mode - for mere mortals at least. Don't expect someone to learn "how to remote" and "how to engineer" simultaneously. It is too much.

4. Establish a physical center of gravity, ideally 20-30% of staff. Company can still be fully remote and have "an office" where company events are held, some fraction of local employees cowork once a week even if on different teams.

5. Regardless of critical mass, all meetings must be remote first. None of this conference room with 10 people dialing into a zoom meeting with 3 other people nonsense. 100ms latency of conversation is real and you are at a disadvantage if you are trying to interject remotely into a room of in person attendees.

6. Hire managers into the critical mass (or who are willing to travel a lot). There will be lots of good reasons for the manager to make their way in on occasion (once a week, twice a month) to the home of critical mass for one reason or another

7. Onboard senior hires and leaders in person. I have seen new leaders, ICs, managers, design/pm/marketing leaders crash and burn over lack of building good relationships in the first 3 months. If you're bringing on a new leader for god's sake make sure they spend a few days in person with the other leaders they have to collaborate with.

8. Hire within a deliberate, manageable timezone range!!! This becomes more important the more varied the experience level is within your team. Is it possible with absolute engineering pros and remote veterans? Yes! But you need to ask yourself if your team is ready to coordinate work across Australia, UK, NYC, SF, Japan, and India timezones. Think hard about this one. My team is US west coast through Czech Republic. Teammates spanning every part of the US, Brazil, UK, Portugal, Denmark, and more.

8.a. Have a clearly established schedule for "time the whole team must be online". For us this is 8:30 - 10:00am Pacific, but many Europeans choose to work shifted schedules to have more overlap with their peers. I advertise this upfront in every hiring manager screen. Make expectations clear and let people decide. We're all adults and we're more likely to commit and make things work when we make a decision with complete information.

9. Onsite time is precious. Don't waste it on ordinary meetings. Use it for strategic conversations, solving hard problems together, hackathons, and high-bandwidth planning. This is where you build the relationships that make the next three months of remote work successful. For fuck's sake please do not fill a week making people stare at a projector while you read powerpoints!!!

Take the advice or don't.

</rant>

Elevated permissions prompts are a massive problem for agents.

What's the general wisdom here on how to handle that without just completely turning off UAC or the Windows Firewall?

LocalMorph is now on Windows! 🎉

Convert video, audio, and images right on your PC. Batch files, trim clips, and extract audio—without uploading your files to a server.

Your files. Your computer.

Get it on the Microsoft Store → localmorph.com

Opus 5.5 can do your job. And mine.

And I mean that for a wide swath of knowledge workers - not just programmers.

So the fact that we are still employed means that either this fact isn't broadly realized, or there is far more to "job" than just the output.

I love the work @burkeholland is doing for high quality Windows apps and that he is putting them on the store for easy access!

apps.microsoft.com/search/publish…

Working on some big updates for his Mirror Me app right now!

DeepSeek releases an "incremental" update for 4.1 Flash that jumps 3 points on DeepSWE and 11 on Terminal Bench. 😳

And now beats 5.6 Sol pretty much across the board.

I got tired of logging-in to USPS *every time* I needed to schedule a package pickup.

So, I made this for me. Free and open source on github. macOS only.

Who’s democratizing evals so that they don’t require a PhD in data science?

Computer Use is sick.

I will never do another expense report. @github Copilot does them now and there is no direct integration required at all.

AI can officially do anything.

UMMMMMM Did someone say canvas support in @code?!??!

GLORIOUS! Copilot app, CLI, and now code!

code.visualstudio.com/updates/v1_142…

I cannot believe this is even real. How is this possible at all.

This is pure sci-fi in real life.

I can't imagine what it was like to watch this in person.

Created a draw/diagram Canvas for @github Copilot app.

Well - Fable did. I haven't created anything in at least a year.

Anyway. Free for you.

github.com/github/awesome…

HydraFusion now has an updated model mix pool, reasoning capabilities, and improved orchestration workflows!

... and we heard a lot of asks for a HydraFusion option to throw at your most ambitious work, and introduced a new Max tier to accommodate those tasks!

We appreciate all your continued feedback :)

github.blog/changelog/2026…