“Once again Saltmarch has knocked it out of the park with interesting speakers, engaging content and challenging ideas. No jetlag fog at all, which counts for how interesting the whole thing was.”
Cybersecurity Lead, PwC
“Very much looking forward to next year. I will be keeping my eye out for the date so I can make sure I lock it in my calendar.”
Software Engineering Specialist, Intuit
“Best conference I have ever been to with lots of insights and information on next generation technologies and those that are the need of the hour.”
Software Architect, GroupOn
“Happy to meet everyone who came from near and far. Glad to know you've discovered some great lessons here, and glad you joined us for all the discoveries great and small.”
Web Architect & Principal Engineer, Scott Davis
“Wonderful set of conferences, well organized, fantastic speakers, and an amazingly interactive set of audience. Thanks for having me at the events!”
Founder of Agile Developer Inc., Dr. Venkat Subramaniam
“What a buzz! The events have been instrumental in bringing the whole software community together. There has been something for everyone from developers to architects to business to vendors. Thanks everyone!”
Voltaire Yap, Global Events Manager, Oracle Corp.
For decades, software systems were built on certainty: declarative programming, deterministic logic, and tests that guaranteed repeatable outcomes. Correctness was defined, provable, and stable. Generative and non declarative systems challenge that foundation. These systems introduce ambiguity by design, producing outputs that are probabilistic, emergent, and negotiated rather than prescribed. This keynote examines what this shift means for how we design, reason about, and trust software. It explores how notions of correctness change when systems no longer strictly obey instructions, and how developers and organizations can navigate ambiguity while still building systems that deserve confidence.
What You Will Learn
How generative and non declarative systems change traditional definitions of correctness
The practical and philosophical implications of building software with probabilistic, emergent behavior
Strategies for managing ambiguity without losing trust in systems and outcomes
Who Should Attend
Software Developers working with AI enabled systems
Software Architects designing modern application platforms
Engineering Leaders and Technical Managers
Anyone responsible for defining quality, correctness, or trust in software systems
