Загрузка видео...

Не удалось загрузить видео

На главную

At Uber, one bug reaching production could cost millions in a single day. So quality was solved with headcount. Rooms of people would manually tap through the app before every release. Request a ride, add a card, cancel a trip, in 50+ languages, release after release. Now coding agents...

377,735 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

One of the most cracked engineers I know believes that local development is (mostly) dead. He walked me through why + his setup for using cloud agents in parallel... The big fucking problem: - You've got one codebase on your computer - Worktrees are supposed to let you run agents in parallel. On a real stack they don't (database contention, port conflicts, a dev server that only works in one tree) - So people flip back to one agent at a time and become the bottleneck themselves - Or they run multiple agents on the same machine: one writes a change, another writes over it, and they're fighting - Then you have to poke around, find everything each agent did, and test it independently - That's too much mental clutter - Locally you're operating like a CPU. You get an instruction, you build it, you queue a backlog The solution: - Stop sharing the computer. Give every agent its own - CJ Hess' setup is Amp "orbs": a full computer in the cloud that clones the repo, starts the dev server, and runs one agent with nothing else contending - A "portal" is a live URL into that running app so you can click around from any device before you trust it - Isolated like an actual team, each person on their own machine The payoff: - It feels like a GPU, not a CPU. A list of 10 tasks, all started, real progress, loop closed - Smaller, contained diffs hit main faster and create fewer conflicts, not more - Favorite prompt: "give me irrefutable evidence that this works." On his laptop he would never run something so heavy he can't use Slack and Chrome. In an orb he will (millions of simulated DB writes, full demo videos) - Smaller diffs, no mixed concerns, higher confidence, ship more often - Mental clutter is gone. One thread, one set of changes, one computer. He always knows the state. That's what lets him do more in parallel, not less - The last things he still does locally: read production logs, set a sensitive secret. He is not spinning up the app on his laptop

Alex Lieberman

98,687 просмотров • 20 дней назад

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 просмотров • 3 месяцев назад