Unit Test
topic on 4 shows · 6 statements across 6 episodes
Latent Space 
No Priors 
the MAD Podcast 
20VC
6 statements about Unit Test, every show
Herzig: Agentic coding succeeds because outcomes are automatically verifiable
“The problem of why does agent decoding work so well, Sarah, is of course you can verify the outcome, right? You can either say, hey, is the program compiling or are your unit tests, right? Does it work, et cetera.”
Coding Agents Should Write AI Model Evaluations Like Standard Unit Tests
“It's like the same way that you would have a coding agent write the unit test. You should have a coding agent write the eval.”
Pereyra: Real software engineering lacks objective unit-test verifiability at scale
“I think you actually have the same problem in programming, where I think in the short term programming is verifiable, where you can look at unit tests, but once you get into real software engineering, like the unit, there is no unit test. It's like I deployed …”
Joelle Pineau: AI benchmarks should be treated as narrow unit tests
“Think of evaluations as, like, unit test for the performance of your system. I mean, software engineers will know what that is, right? Like, you run through that evaluation, and that gives you, like, a signal of how the system is doing in a particular dimensio…”
Albrecht: Imbue is currently writing unit tests automatically using its AI agents
“We're writing unit tests literally right now automatically.”
Mathew Lodge: Developers dislike unit tests because incentives favor feature delivery
“Fundamentally they're not paid to write tests. They're paid to deliver the functionality, the new things in the application that fixes the application, the updates and tests are just there to, as part of the process to help them.”