The Typo That Broke Production — And Accidentally Created Spring Cloud Contract • Marcin Grzejszczak & Jakub Pilimon

This interview was recorded for GOTO Unscripted.https://gotopia.techMarcin Grzejszczak - Software Engineer at HeroDevs & Java ChampionJakub Pilimon - Software Architect at jPilo & Software Consultant at Bottega IT MindsORIGINAL TALK TITLEThe Typo That Broke Production — And Accidentally Created Spring Cloud ContractCheck out more here:https://gotopia.tech/articles/435RESOURCESMarcinhttps://bsky.app/profile/toomuchcoding.comhttps://mastodon.social/@[email protected]://twitter.com/MGrzejszczakhttps://github.com/marcingrzejszczakhttps://www.linkedin.com/in/marcin-grzejszczak-15565119https://toomuchcoding.comJakubhttps://twitter.com/JakubPilimonhttps://github.com/pilloPlhttps://www.linkedin.com/in/jakub-pilimon-449b7984http://pillopl.github.ioLinkshttps://toomuchcoding.com/posthttps://martinfowler.com/articles/consumerDrivenContracts.htmlhttps://www.tomakehurst.comDESCRIPTIONIn this GOTO Unscripted episode, Jakub Pilimon sits down with Marcin Grzejszczak — Java Champion, Spring Cloud Contract contributor, author, mentor, and founder of a rural housewives' circle (yes, really) — to trace a 15+ year career that went from C++ on the Côte d'Azur to becoming one of the key architects of Spring Cloud Contract and the Micrometer Observation API. Marcin shares how real production pain — a junior dev fixing a typo in an API that silently broke every client — gave birth to what would become Spring Cloud Contract, and how he's never shy about calling out his own embarrassing code (complete with a Javadoc that opens with "I'm sorry").The conversation pivots sharply into 2025 territory, with Marcin sketching out an AI-powered future for contract testing: instead of manually writing contracts (which developers routinely abandon), capture live production traffic, let AI generate the contracts, and let humans do what they're actually good at — reviewing and approving. Wrapping up with observability, Marcin argues the most underrated pillar isn't logs, metrics, or traces — it's context. Without knowing why something happened (a deployment, a business event), raw telemetry data is just noise. Practical, honest, and occasionally self-deprecating: a thoroughly human conversation in the age of AI.RECOMMENDED BOOKSMarcin Grzejszczak • Mockito Cookbook • https://amzn.to/4rXOrtfMarcin Grzejszczak • Instant Mockito • https://amzn.to/4lV2ePQSam Newman • Building Microservices • https://amzn.to/3dMPbOsSam Newman • Monolith to Microservices • https://amzn.to/2Nml96ERoy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNBCharity Majors, Liz Fong-Jones & George Miranda • Observability Engineering • https://amzn.to/38scbmaBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!