Home Gotopia Articles The Typo That Br...

The Typo That Broke Production — And Accidentally Created Spring Cloud Contract

In this GOTO Unscripted episode, Jakub Pilimon sits down with Marcin Grzejszczak to trace his 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.

Share on:
linkedin facebook
Copied!

About the experts

Marcin Grzejszczak

Marcin Grzejszczak ( expert )

Software Engineer at HeroDevs & Java Champion

Jakub Pilimon

Jakub Pilimon ( interviewer )

Software Architect at jPilo

Read further


In 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.