Explore >> Select a destination
|
You are here 
|
semver.org | ||
| | | | |
kidger.site
|
|
| | | | | Personal website. Math, SciML, scuba diving! | |
| | | | |
bernat.tech
|
|
| | | | | The DRY principle (an acronym for don't repeat yourself) encourages software engineers to abstract code into a separate component and reuse it rather than write it over and over again. If this happens across the system, the best practice is to put it inside a package that lives on its own (a library) and then pull it in from the applications when required. As most of us can't think of every feature that the library might offer or what bugs it might contain, these packages tend to evolve. Therefore, we need some mechanism to encode these evolutions of the library, and most commonly, this is a version number. | |
| | | | |
jacobtomlinson.dev
|
|
| | | | | Version numbers are hard to get right. Semantic Versioning (SemVer) communicates backward compatibility via version numbers which often lead to a false sense of security and broken promises. | |
| | | | |
xnacly.me
|
|
| | | Guide and example on how to configure the coc.nvim extension and lsp provider (config and keybinds) | ||
