When Kimmy first poked her head out of that bunker a lot had changed in the world around her. Armed with only the finest cultural memes of the late 90's, she stepped out of the bunker and into her new life. Lucky for Kimmy, people are adaptable and are able to absorb a few cultural version changes pretty easily. Despite the prefix, software is rarely so flexible.
Semantic versioning has introduced a whole new way to think about what version numbers mean. Properly practiced, semantic version numbers communicate a lot about what's going on in a given software release. When consuming a library or framework, what can you learn from their version number? On the flip side, how can you properly release semantically versioned code? What is a breaking change? What is a deprecation? Leaving this talk you'll have a solid understanding of what it means to establish public contracts for your code, how to go about properly versioning those contracts, and even test to be sure you're adhering to them. As a library consumer, you should walk away from this talk better suited to deal with changes to your dependencies and poised to make your applications unBreakABLE.