bhl

gh pr diff [num]

also works if you have the GitHub cli installed. Would setup an AGENTS.md or SKILL.md to instruct an agent on how to use gh too.

It does not matter what 80-90% of developers do. Code development is heavily tail-skewed: focus on the frontier and on the people who are able to output production-level code at a much higher pace than the rest.

Multi-agents.

Not for us to question or answer though.

What’s the solution here, reward code that works without try catch, reward code that errors and is caught, but penalize code that has try catch and never throws an error?

Cursor will pivot to a computer use company.

The gap between coding agents in your terminal and computer agents that work on your entire operating system is just too narrow and will be crossed over quick.

> Originally, it was all about quality data sources.

It still is! Lots of vertical productivity data that would be expensive to acquire manually via humans will be captured by building vertical AI products. Think lawyers, doctors, engineers.

Not all will become OSS. Some will become products, and that requires the best people.

The moat is people, data, and compute in that order.

It’s not just compute. That has mostly plateaued. What matters now is quality of data and what type of experiments to run, which environments to build.

Hiring is always a sh*tshow. The only thing that matters is survival: keep applying, keep grinding, keep growing.

And if there's any opportunity to show off, don't be shy :)

Stacked diffs is a huge one, and also where improving git would also improve LLM workflows. The bottleneck after code generation is PR reviews, and stacked diffs help break down large PRs into more digest-able pieces.

If you help humans collaborate better, you help LLMs collaborate better.

Mobile has really strong offline-primitives compared to the web.

But the web is primarily where a lot of productivity and collaboration happens; it’s also a more adversarial environment. Syncing state between tabs; dealing with storage eviction. That’s why local first is mostly web based.

IIRC, Kleppmann built a prototype for it but it’s not included in Automerge yet.

1. You can use TipTap with it: just have to wrap your existing schema with automerge attributes. Undo redo would also swap out.

> The Codex sprint was probably the hardest I've worked in nearly a decade. Most nights were up until 11 or midnight. Waking up to a newborn at 5:30 every morning. Heading to the office again at 7a. Working most weekends.

There's so much compression / time-dilation in the industry: large projects are pushed out and released in weeks; careers are made in months.

Worried about how sustainable this is for its people, given the risk of burnout.