Rotem Meidan

Rotem Meidan

Besides being a husbad and father, Rotem is a software engineer and manager, open source advocate, focusing on developer experience and building developer tools for over 13 years. Passionate about optimizing development flows, for both humans and agents, learning and educating when I can. Creator of returnzero.dev In his current role at Taboola, Rotem has a dual mission: to make ADLC transparent, measurable and steerable, and make the CI feedback loop blazingly fast, to support the 10x PRs ADLC brings with it.
You Can't Improve What You Don't Measure: Making Agentic Coding a Measurable Engineering Discipline
AI Coding Summit Asia 2027AI Coding Summit Asia 2027
Upcoming
You Can't Improve What You Don't Measure: Making Agentic Coding a Measurable Engineering Discipline
We run production services with monitoring, SLOs, alerting, and postmortems. We do all that to watch the system, improve it, and act quickly with a short feedback loop. With coding agents, we review the final output and monitor token usage and spending, but rarely measure whether new context, skills, or tools improve the output. We almost never review the process, and how can you improve the process if you don't measure?
This talk makes an attempt at introducing a method for monitoring and improving ADLC, making the process visible by scoring it end to end: intent clarity, context quality, local tool calls, CI runs, PR outcome, and how the change survived production. Each failure signal maps to a treatment (context, skills, tools, guardrails), giving engineers a way to improve ADLC with the same rigor they apply to production systems.
Detox: The Unobtainable Test Stability (or is it?)
TestJS Summit - January, 2021TestJS Summit - January, 2021
36 min
Detox: The Unobtainable Test Stability (or is it?)
In this talk, we'll discuss how Wix is using Detox internally, how we manage configuration, how we fight flakiness, and some best practices we've developed over the ~3 years of building and using Detox in our CI process. We'll also discuss our endless striving for "0 manual QA", which always seems in reach, if we only overcome that one last technical hurdle.