Semantic versioning (SemVer) is a widely accepted method for naming software versions, structured as major.minor.patch numbers. Major versions indicate breaking changes, minor versions signal new features that don't disrupt existing functionality, and patch numbers relate to bug fixes. Despite its popularity, the author argues that SemVer often misrepresents the impact of changes. Many consumers of APIs don’t use the entire contract, which can lead to an overestimation of how likely a version change will cause issues. Conversely, they might rely on undocumented features, causing an underestimation of potential breakages. The article highlights practical issues with SemVer. Small performance enhancements or subtle behavior changes often go unrecorded in version numbers, and developers frequently misclassify changes as either breaking or non-breaking. The author emphasizes that when his teams face breakages after dependency upgrades, SemVer fails to provide effective guidance. Even those who advocate for SemVer often overlook its implications, particularly the significance of the major version zero, which theoretically allows for any change. The author notes the irony that while SemVer is touted as important by leadership, they often neglect the necessity of a clearly defined API contract. The critique extends beyond technical shortcomings to a cultural observation in software development. The author defines "Smart Person Recommendations" as widely endorsed practices that lack rigorous questioning. While some recommendations, like thorough documentation and automated testing, have clear benefits, SemVer might not be one of them. In the end, the article challenges the assumption that SemVer is inherently superior to other versioning strategies, suggesting that it may simply be a trend rather than a definitive solution.