Luca Ingianni

Things Luca Says on Podcasts

Embedded software consultant working on agile methods, requirements engineering and continuous integration for embedded systems teams. One of two consultants who, by his own account, started a podcast almost by accident while working from opposite sides of the world. Co-hosts The Agile Embedded Podcast (renamed the Pragmatic Embedded Podcast after five years and 101 episodes) with Jeff Gable, and has appeared as a guest on Embedded.

Where to Find Them

Luca Ingianni hosts and writes The Agile Embedded Podcast . They have also been a guest on Embedded .

Recently: “Why Testing Sucks, Revisited” on The Agile Embedded Podcast (November 2026); “Testing Embedded Systems in the Cloud and On-Prem with Marie Meyer and Joel Schulz-Andres” on The Agile Embedded Podcast (October 2026); “TDD: The Hard Parts - Getting Started with Test-Driven Development” on The Agile Embedded Podcast (September 2026); “TDD: The Hard Parts - Getting Started with Test-Driven Development” on The Agile Embedded Podcast (September 2026); “The Big Rename: From Agile to Pragmatic” on The Agile Embedded Podcast (September 2026); “The Big Rename: From Agile to Pragmatic” on The Agile Embedded Podcast (September 2026).

What They Said

“I would be much more comfortable with the LLM rewriting large swaths of production code if it doesn't touch the tests than the other way around.” — Luca Ingianni, The Agile Embedded Podcast

Jeff had said LLMs will happily refactor big chunks of code, where unit-test friction used to discourage refactoring. Luca replies that letting an LLM rewrite the test suite without oversight carries risks you may not notice.

The Agile Embedded Podcast · 2026-11-18 Permalink → Listen →
The Agile Embedded Podcast Around 10:33 into the episode
Luca Ingianni

because if you allow an LLM to rewrite your test suite without sufficient oversight, which then again slows you down because you need to actually pay attention, you may introduce risks that you're not even aware of and that will come back to bite you at the worst times.

Jeff Gable

Yeah, it's true. It's just like it's just like any aspect of writing code with an LLM, you know, you have to, you have to make that balance of what level of oversight you want to apply to it. But I

Luca Ingianni

think the bottom line is I would be much more comfortable with the LLM rewriting large swaths of production code if it doesn't touch the tests than the otherwise.

Jeff Gable

Yes. And so maybe at that point, maybe we have more and more integration tests. Maybe I am coming back around to the fat middle where you have lots and lots of integration tests because they tend to survive. Yeah, these tend to be more stable because they're higher level. They survive refactoring.…

Luca Ingianni

Actually, I wanted to ask a question. Yes. Have you or are you in the habit of removing unit tests at some point after they've been written?

Jeff Gable

I was thinking about that as well. I wouldn't hesitate to advocate for that if it fits, say, a client's situation if I were working with someone. I have found that I do not just because, again, I do that rapid prototyping, but then once I build a module for a medical device, that module is going to…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“LLMs love creating mocks and mocking all of the things, and it just is not going to be very helpful. So I advocate for keeping LLMs on a very tight leash if you are using them to write tests, as you should. … Whenever I have an LLM generate test suites for me, I will always find out like 90% of the test cases are fantastic and do exactly what I want. And the other 10% are just garbage. You must never let go of the reins when it comes to LLMs.” — Luca Ingianni, The Agile Embedded Podcast

Jeff had argued that LLMs make test infrastructure cheap to build. Luca agrees they lower the activation energy but warns about what they produce when asked to write test suites.

The Agile Embedded Podcast · 2026-11-18 Permalink → Listen →
The Agile Embedded Podcast Around 33:52 into the episode
Luca Ingianni

…that was fully intended to be simple and sort of cutting a couple of corners and not actually being production ready, it just had to be Luka ready and sort of give reasonable benchmarking results. It is a lot of work. So be careful what you're setting out to do because it has a habit of ballooning.

Jeff Gable

Fair enough.

Luca Ingianni

And by the way, case in point, to get back to the topic at hand, the same will happen if you use an LLM to write test suites for you because they love writing tests. They will write all of the tests. And in fact, they will write all of the mocks. I hate that so much. LLMs love creating mocks and mocking all of the things and it just is not going to be very helpful. So I advocate for keeping LLMs on a very tight leash if you are using them to write tests as you should. I absolutely say you should use them because it lowers, just like you said, Jeff, that activation energy. It makes it much more inviting to actually write tests, but you still need to be in control of the entire thing. You still need to consider test cases and ask, well, is this a worthy test case? And then is it actually implemented in such a way that it will remove the risk that I'm worried about? Because whenever I have an LLM generate test suites for me, I will always find out like 90% of the test cases are fantastic and do exactly what I want. And the other 10% are just garbage. So you must learn. I'm sorry, I keep going on about this. Because that has been the thing that has been most on my mind for the last couple of months. You must never let go of the…

Jeff Gable

way. Yeah. All right. I think we're running long on time, so that's probably a good place to cut it. Yes. I like it. Yeah. Why testing sucks, revisited?

Luca Ingianni

Yes. Well, does it still suck? Or did it suck to begin with? I don't know. What's your take?

Jeff Gable

Oh, I don't know. That's just a clickbaity title. Let's be honest here. Right. So, anyway, I hope that discussion was useful and valuable for you and maybe made you think about some new perspectives. Luca, where can people go to find you online?

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In