imo these 2 affect business' ai productivity the most:
Fragmentarion - every local setup prevents raising the floor
Weakest link - all gains are throttled by the most constrained component (spending caps, avail models, MCP access, Slack v gChat integration, shared harness)
Fragmentarion - every local setup prevents raising the floor
Weakest link - all gains are throttled by the most constrained component (spending caps, avail models, MCP access, Slack v gChat integration, shared harness)
2
0
4
412
Opus 5.5 > Sol 6.1
Maybe I'm late, but I couldn't get Sol to nail down why passkeys weren't working in T3 Code.
Opus showed me how there's an Electron limitation that Codex Desktop doesn't run into because it ships a web_authn.node shim.
Then it patched the nightly with a fork
Maybe I'm late, but I couldn't get Sol to nail down why passkeys weren't working in T3 Code.
Opus showed me how there's an Electron limitation that Codex Desktop doesn't run into because it ships a web_authn.node shim.
Then it patched the nightly with a fork
4
0
14
1,161
"opus fork t3 code and make the in-app browser work with SSO passkeys like codex desktop"
Quickly becoming my daily driver. Auto-settling on PR merge is what everything should do
Quickly becoming my daily driver. Auto-settling on PR merge is what everything should do
3
0
7
762
Man, its humbling seeing what the Agents eXperience is able to build
Even side-quests have tons of polish and intention
(also @acoyfellow is just the nicest guy)
Even side-quests have tons of polish and intention
(also @acoyfellow is just the nicest guy)
2
0
16
647
Eric Clemmons 🍊☁️ retweeted
Automatic retries for Durable Objects are here!
We are now retrying fetch and RPC calls to your Durable Objects automatically in the runtime, zero code changes needed.
We do have some config that allows you to make them more powerful, details below 👇
We are now retrying fetch and RPC calls to your Durable Objects automatically in the runtime, zero code changes needed.
We do have some config that allows you to make them more powerful, details below 👇
13
27
213
21,383
Eric Clemmons 🍊☁️ retweeted
Congratulations and thank you to Texas Republicans for electing James Talarico (D) as our next senator.
6
6
171
24,718
"Hey opus, look at the commit history for this repo and give me concrete examples of how PBT/MBT/Oracles would've made a huge impact. I'm looking for a holy crap reaction from the team."
(minutes later)
Holy crap 🤯
(minutes later)
Holy crap 🤯
7
5
295
24,649
Eric Clemmons 🍊☁️ retweeted
“how do I know if I have healthy systems, fast software, and happy users?”
great question. observability. choose basically whatever tool you want. managed, self hosted, open source, who cares. I use Datadog.
> implement otel tracing in this repository. export to datadog. add tracing to all of my hono route handlers, middleware, and helpers. anything that makes an async request should be traces /at the function definition/. avoid doing inline tracing and focus on definitions. any async function that’s exported should be traced. add a lint rule to verify this behavior. make sure the request context (business id, user id, outcome, etc) are attached to every span emitted. consume incoming traceparents and forward them to other services
> read loggingsucks.com by @boristane and implement it everywhere
easily two of the highest ROI prompts you can do on an underobserved production system. if you don’t know what’s happening in production, your p0 is doing that.
great question. observability. choose basically whatever tool you want. managed, self hosted, open source, who cares. I use Datadog.
> implement otel tracing in this repository. export to datadog. add tracing to all of my hono route handlers, middleware, and helpers. anything that makes an async request should be traces /at the function definition/. avoid doing inline tracing and focus on definitions. any async function that’s exported should be traced. add a lint rule to verify this behavior. make sure the request context (business id, user id, outcome, etc) are attached to every span emitted. consume incoming traceparents and forward them to other services
> read loggingsucks.com by @boristane and implement it everywhere
easily two of the highest ROI prompts you can do on an underobserved production system. if you don’t know what’s happening in production, your p0 is doing that.
more bangers for those who like healthy systems, fast software, and happy users
> find every place we load a whole row from the database just to read a couple of fields. instead, select only what we need
> remove all unnecessary `new URL()` parsing
> compute all regexes at the module level instead of instead functions and loops
> find hot-path reads of a single key from a large jsonb column and promote that key to a real column
(avoid large jsonb like the plague if you can)
before doing that last one, we had queries that had to detoast 20gb+ of data just to need a couple of kb. highly recommend.
what else do people need?
18
13
441
42,288
Eric Clemmons 🍊☁️ retweeted
😴 rest easy - Durable Objects can now wait until they hibernate to apply code updates, giving long-running agent turns time to finish even if you're shipping PRs by the second.
developers.cloudflare.com/changelog/post…
developers.cloudflare.com/changelog/post…
11
11
68
8,409
Eric Clemmons 🍊☁️ retweeted
TanStack DB 1.0 RC1 is out!
Backend data that feels local: typed collections, live queries, and edits that show up instantly, then sync.
Start with your REST API. Add persistence, offline writes, and real-time sync later. Your queries stay the same.
Backend data that feels local: typed collections, live queries, and edits that show up instantly, then sync.
Start with your REST API. Add persistence, offline writes, and real-time sync later. Your queries stay the same.
28
96
1,299
119,232
Eric Clemmons 🍊☁️ retweeted
Me and a band of plucky misfits (@maks_mak_0 and a few others), codename the Alertocats 🙀, have started rebuilding Cloudflare's whole notifications and alerting experience.
First up: a brand new UI. Find it in the dash at Observability → Alerts 👇
First up: a brand new UI. Find it in the dash at Observability → Alerts 👇
16
21
135
27,458
IMO agent-first CI means:
1. Do less work, faster
2. Consistent everywhere
3. Event-driven loop, not just commits
1. Do less work, faster
2. Consistent everywhere
3. Event-driven loop, not just commits
6
1
26
2,307
Not just AWS…
Amazon's leadership is very good at writing, but you still need to read between the lines.
What I read between these lines:
Engineers who are not "product engineers" (aka eng + PM interest) and don't like to be customer-facing will not have a future inside of Amazon
Full: aboutamazon.com/news/company-n…
0
0
7
684
Eric Clemmons 🍊☁️ retweeted
Today one of our Engineers at @amini_swiss built a showcase / explainer / demo for @CloudflareDev Durable Objects.
It's beautiful and therefore would love to share it with TPOT.
>> durable.ami.ni
It's beautiful and therefore would love to share it with TPOT.
>> durable.ami.ni
9
7
61
6,315
Tried "steer" instead of "queue" for a week...
Prompt: "<14 comments on implementation> Fix these"
Steer: "...and remove tests until I'm happy with the impl"
Sol: "Removed those tests for you. No other changes."
😵💫
Prompt: "<14 comments on implementation> Fix these"
Steer: "...and remove tests until I'm happy with the impl"
Sol: "Removed those tests for you. No other changes."
😵💫
19
1
128
10,597
Eric Clemmons 🍊☁️ retweeted
Motherload solves the typesafe .env problem (getting autocompletion on process.env), no schemas required.
1. Import a .env file
2. That's it
1. Import a .env file
2. That's it
45
42
815
46,205
Eric Clemmons 🍊☁️ retweeted
New: domain-driven design for Effect, in alchemy.run/domain.
Translate business requirements directly into working software and integrate into your alchemy infrastructure.
Translate business requirements directly into working software and integrate into your alchemy infrastructure.
16
23
464
34,710