Explore >> Select a destination
|
You are here 
|
gavinhoward.com | ||
| | | | |
semver.org
|
|
| | | | | Semantic Versioning spec and website | |
| | | | |
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. | |
| | | | |
chrispenner.ca
|
|
| | | | | The Personal blog and musings of Chris Penner, a designer, developer and future opsimath. | |
| | | | |
www.softdevtube.com
|
|
| | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | ||
