Copy article about codebase design into clean code
This commit is contained in:
parent
e7e1e854e4
commit
48693ee10d
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user