Hey @Rogers, adding a 1.6% fee to pay your Rogers bill with the Rogers Credit Card penalizes the exact use its cashback bonus is built for. I have this card because I'm a Rogers customer. Now that loyalty costs me $48 a year. #taxes
@johnternus I thought it was a joke seeing it from someone on social media… well, it was not a parody.
Glue an iPad on a HomePod and you get a HomeView 🤔
Versioned, diffable, zero infrastructure. The "why" lives in git where engineers already look.
No session server, no new platform — just the distilled intent committed with the code.
You need git for conversations, not just code. A shared session server where every agent run is visible, forkable, and attachable to a PR. The diff shows what changed. The conversation shows why. OpenClaw's team server model at DevDay is the closest thing I've seen working.
While everyone's talking about agents, I've been exploring how teams can use them to work better together.
Here’s my take, from OpenAI DevDay 2026. https://t.co/W3rVoiTo84
Decisions are the signal. Conversations are the noise that produces the signal.
I keep a decisions artifact in the repo, updated alongside every code change in the same PR.
Next gap in SDD: specs are still prose. Traceability is checkable; correctness and consistency are still judgment.
Missing layer: structure beneath the prose (entities, relationships, invariants), so "does the output satisfy the source?" becomes checkable.
If code becomes disposable and regenerable, the spec is the real artifact.
The scarce skill isn't generating software anymore. It's stating precisely what must be true, which most organizations have never had to practice at scale.
Paid a small fortune for this book - I want to understand how the sudden advancement in technology+computing in 1982 should have meant the end of needing any programmers to build software
As this topic is very relevant again, with the sudden advancement w technology+computing
Spec-driven development like Linked-Intent Development is a working answer to this: the spec is the source, code and tests are regenerable output, every behavior traces to a spec ID.
Delete the code, rebuild from the intent docs. That's the bar.
https://t.co/FyyxJ7t4S4
My keynote at LDX3 New York, "The state of the tech industry in 2026". is out now. Timestamps:
00:00 Introduction
00:53 What changed
12:29 What's not changed
16:14 What broke
22:53 What’s next
And for notes + slides, see: https://t.co/XZ2V1P70mH
Hope it's useful!
An API can say a refund endpoint takes an amount and a customer ID. It can't say "refunds over $500 need approval unless the account is in good standing, and never after 90 days."
That rule lives in docs, code, and people's heads. A spec an agent can read puts it in the contract.
We are making Markdown files work natively across Google Drive and Docs.
You can now preview .md files in Drive, open them in Docs, edit them, comment on them, and collaborate without converting the file into a Google Doc!