43:I[185,["/_next/static/chunks/0sxns9k8ywops.js","/_next/static/chunks/11fk-1ie3w6mp.js","/_next/static/chunks/1uc4qdk4uj22c.js","/_next/static/chunks/0jvahffpql9nd.js","/_next/static/chunks/0agcep-t686m_.js","/_next/static/chunks/2_mrasy1s2owt.js","/_next/static/chunks/1nsk8jrr9fqe6.js"],"SendEmailButton"] 45:I[63625,["/_next/static/chunks/0sxns9k8ywops.js","/_next/static/chunks/11fk-1ie3w6mp.js","/_next/static/chunks/1uc4qdk4uj22c.js","/_next/static/chunks/0jvahffpql9nd.js","/_next/static/chunks/0agcep-t686m_.js","/_next/static/chunks/2_mrasy1s2owt.js","/_next/static/chunks/1nsk8jrr9fqe6.js"],"AddToLibraryButton"] 46:I[29721,["/_next/static/chunks/0sxns9k8ywops.js","/_next/static/chunks/11fk-1ie3w6mp.js","/_next/static/chunks/1uc4qdk4uj22c.js","/_next/static/chunks/0jvahffpql9nd.js","/_next/static/chunks/0agcep-t686m_.js","/_next/static/chunks/2_mrasy1s2owt.js","/_next/static/chunks/1nsk8jrr9fqe6.js"],"ShareButton"] 47:I[58016,["/_next/static/chunks/0sxns9k8ywops.js","/_next/static/chunks/11fk-1ie3w6mp.js","/_next/static/chunks/1uc4qdk4uj22c.js","/_next/static/chunks/0jvahffpql9nd.js","/_next/static/chunks/0agcep-t686m_.js","/_next/static/chunks/2_mrasy1s2owt.js","/_next/static/chunks/1nsk8jrr9fqe6.js"],"ProcessEpisodeButton"] 48:I[45269,["/_next/static/chunks/0sxns9k8ywops.js","/_next/static/chunks/11fk-1ie3w6mp.js","/_next/static/chunks/1uc4qdk4uj22c.js","/_next/static/chunks/0jvahffpql9nd.js","/_next/static/chunks/0agcep-t686m_.js","/_next/static/chunks/2_mrasy1s2owt.js","/_next/static/chunks/1nsk8jrr9fqe6.js"],"SignupCTA"] 3b:["$","time",null,{"dateTime":"2026-04-25T16:00:00.000Z","children":"April 25, 2026"}] 3c:["$","span",null,{"aria-hidden":true,"children":"·"}] 3d:["$","span",null,{"children":"00:23:08"}] 44:T52d,

In this episode of The Agile Software Engineering Deep Dive, Alessandro Guida explores the gap between engineering quality and customer-perceived quality.

While engineers often define quality in terms of architecture, testing, and process, customers evaluate it through experience: whether the software works, whether it is easy to use, whether it is reliable, and whether it performs without friction.

The episode reflects on why many essential engineering practices remain invisible when they work well, why elements like security are expected but rarely noticed, and how this disconnect can lead teams to optimize for the wrong signals.

If you are building software in complex environments, this episode offers a grounded perspective on how to align engineering discipline with what truly defines quality from the outside.

Support the show

This Podcast is an audio version of the written Agile Software Engineering newsletter. If you want to go deeper, don't forget to subscribe the newsletter too.