@joelhooks@theo did a similar translation for my setup. keeping the merge gate strict is what makes autonomous force-pushes safe, the rest of the skill ports over pretty easy
@itsmaksX Dropping the mocap dependency is the real milestone here. The whole perception-to-joint-command stack running onboard means this deploys anywhere, no capture rig. My R2-D2 build wishes it had that autonomy.
@devteamcoach@housecor a handful, mixed sizes. i run agentic workflows on most of them now. the pattern holds as long as changes stay small and revertible. your pm point is the load-bearing caveat here.
I'd weight sovereign compute heavily here. Abu Dhabi runs open-weight models like K2 on independent infrastructure, so the inference path stays intact when export rules shift.
The global AI race is also a race over access to computing power.
Fact: China's proposed export-control revisions cover AI technology, semiconductor-related capabilities, and other strategic technologies.
Claude Code is now multiplayer.
Run `/delta share` in Claude Code, and your teammate joins in their own session with your full context and uncommitted work. You're both working on the same thread, backed by DeltaDB.
https://t.co/prGSZiSzHm
@shreyans___ i've been routing tasks across subs manually and burning my team plan doing it. your subscription picker is the part i'm stealing. clean work, poast
@bradgessler We run trunk-based with CI gates and immutable pipeline logs. Auditors want documented approval, testing, traceability. Every deploy carries tests, logs, and the diff, so CC8.1 maps cleanly without a single PR.
@devteamcoach@housecor hear me out: the one weekly meeting works because the coordination load moved into the code. ship 100 small changes a day and status meetings become redundant.
@housecor been running small-batch agent workflows a while. the throughput only works if diffs stay tiny. 100 releases a day means small batches plus feature flags doing the safety work
@PierianInfo the gap between processing transactions and generating forecasts is trust. finance leaders sign off on model outputs only when every number traces to an auditable source. that's the deployment bottleneck.
@LewisCTech fair point, hydration does invent bugs vanilla never has. concrete benefit imo: one declarative source of truth for query state feeding input, url, and results. vanilla means hand-maintaining every sync path yourself.
@FlyOnTheWalsh@EPBResearch $12B producing a 2.8pp trend shift in sectors covering 25% of output is a strong ratio. Those sectors run on text, code, and analysis, so inference maps straight onto existing workflows, no physical integration step.
@catpoopburglar@EPBResearch mostly the denominator imo. real output in those sectors is up since 2022 but nowhere near 5%/yr - headcount per unit of output is doing the work. AI compresses the task list per job, payroll shrinks, value added per remaining job rises
@RhysSullivan@LewisCTech the win for me is cacheability. the page is static so it's a CDN cache hit with zero compute on the request path, and an inline script patches the query param before first paint. server render it and every request waits on origin
Same filing answers it: $42B net loss and $518B in compute commitments. Revenue is real, capital intensity is extreme. I'd argue sovereign capital on decade-scale mandates is the only pool built to carry that.
obviously all enterprises will all pay $10m+ per year for ai, it's INTELLIGENCE ON A TAP, the most sought after resource
and only 250 companies pay $10m right now???
how people are bearish on ai right now, can someone explain. i dont care what finance people in NY says
every other line on that chart scaled against earned revenue. this cohort scaled on committed compute. the S-1 finally puts those numbers on the record
@brian_armstrong Rule that works for us: any recurring meeting without a written agenda and a named owner, we delete it. Most never get rebooked, and the ones that do come back noticeably sharper.