From 48693ee10d8634fe2905dd753981558d748d850b Mon Sep 17 00:00:00 2001 From: Morgan Date: Wed, 23 Jun 2021 08:57:20 +0200 Subject: [PATCH] Copy article about codebase design into clean code --- sections/programming.md | 1 + 1 file changed, 1 insertion(+) diff --git a/sections/programming.md b/sections/programming.md index dd01f6f..ee96b23 100644 --- a/sections/programming.md +++ b/sections/programming.md @@ -801,6 +801,7 @@ See also [Calm programming / Slow programming](#calm-programming--slow-programmi > * Software do not have a technical debt problem, software simply requires maintenance. * [Kailash Awati](https://eight2late.wordpress.com/2009/07/16/maintenance-matters/) - (2009) Maintenance matters > * Maintenance is a solution, not a problem. **See also** [Robert Glass](http://www.robertlglass.com/)‘ wonderful book, [Facts and Fallacies of Software Engineering](https://www.goodreads.com/book/show/83792.Facts_and_Fallacies_of_Software_Engineering) and [my highlights from this book](../books/facts_fallacies_software_engineering.md) +* [Kamil Grzybek](https://www.kamilgrzybek.com/design/feature-folders/) - (2018) Feature Folders | on codebase design > Tools * [Semver check](https://jubianchi.github.io/semver-check/#/) - More and more projects try to follow Semantic Versioning to reduce package versioning nightmare and every dependency manager implements its own semantic versioner. Composer and NPM for example don't handle version constraints the same way. It's hard sometimes to be sure how some library version will behave against some constraint. This tiny webapp checks if a given version satisfies another given constraint.