Regressions happen. But you don't want to find out from app store reviews or spicy…
This is a dev post classified by Jev as Testing & observability (a tool drop), kept by the Dev Radar because it carries real work, not commentary.
Regressions happen. But you don't want to find out from app store reviews or spicy reddit comments. With our Observe service you can see which release caused a regression and what kind of devices are experiencing it. And then you can hand your agent a prompt with the data to fix it. It's good to ship and touch grass. It's more relaxing with Observe: https://try.expo.dev/observe-regression
Posted by Expo (89.6k followers) 1 days ago · 101 likes · 6.4k views · view the original post on X. Kept by the Dev Radar as Testing & observability. Tools mentioned: Expo.
More dev work like this
- What does observability look like when a judgment costs nothing? — @hugorcd
- When agent traces turn into a debugging pile, this repo gives you a place to inspect them. — @DanKornas
- I’m glad @strawgate's standards for coffee are lower than his standards for code review… — @kayvz
- Gitar finds bugs, fixes them under your team's rules, and verifies every fix by running… — @SonarSource
- One AI agent is easy to monitor. 1,000 agents running across your org? Different problem. — @AlphaSignalAI
- OPENAI 🔥: Chrome extensions are now supported in the ChatGPT desktop browser! — @testingcatalog
- e2e + jev from @typesafeai ⚡ — @o_kwasniewski
- AI at scale needs visibility to match. — @splunk
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 14.4k posts from 4.7k X accounts over the last 21 days, 1.6k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 19:58 UTC. Full method.