Sonar

And I, I have a statistic in my, my talk I'm gonna give later where there was a company called Tidelift.

They've been since acquired, um, by Sonar, SonarSource, uh, acquired them.

But they did, they used to do this yearly survey of open source developers, and the last one they did was in 2024, and basically they would ask developers, like, "How are you doing? Are you over...

Like, are you thinking about quitting? Have you quit? What's going on?" And in 2024, 60% of open source developers were saying they've quit or thinking of, of quitting, where they're just, they're, they're done.

Deciding which one is doing valuable work takes more than just PRs merged.

Joining me today to talk about it is, uh, Andrea Malagodi, CTO at Sonar, which provides AI code verification and governance for shipping code with confidence.

Andrea, how are you feeling about software engineering today? And it's great to see you.

Uh, thank you very much for having me.

So yes, it's good to have numbers, uh, and we should be very careful to not pass, uh, judgment too quickly without really understanding the context of the problems that are being worked on and the, the, the, the issues that's being tried to be solved or the opportunity that's being explored.

Uh, it was a great learning for me, and the best part of that probably was to get this individual that was essentially making using AI part of his craft, and then being able to obviously share that to, you know, other engineers so they can take benefit for it.

Um, within that, of course, Sonar focuses on this, uh, fundamental idea of trying to guide the AI, verify the outcome, and, you know, most of us work on brownfield applications of some sort, so there is a backlog of things that can be solved by, for example, remediation agent that can go and look at all past issues, or now also hunter agent that can go and look at security, um, issues that may not necessarily be found in the upfront workflow or be part potentially of legacy code that needs to be inspected anew.

It's funny because I think we were having this debate a couple of years ago, uh, broadly as a community about velocity and lines of code and people over-optimizing for them, um, and understanding the value cycle of software and the differences between different projects.