The following articles and books are the ones I found most impactful throughout my software engineering career. "Impactful" here means sources that:

• I agree with
• are not included in every single beginner tutorial on the web (and indeed mostly contradict them!)
• helped me build maintainable software

Note that great books and posts might be excluded if I read them but already knew all their concepts from other sources (i.e. they had no impact).

Do not understand these sources as a learning guide for you! The goal of this repository is to enable me to revisit my most important sources and for others to understand the principles of my software engineering.

The sources below are ordered by the time I found and read them.

Book "Dependency Injection" by Mark Seemann

DI and IoC are mentioned in almost every tutorial about how to grow an application from beginner level to useful enterprise code. This book, however, is the only source I ever found that states when to use DI and even more importantly when not to.

Book "Growing Object-Oriented Software, Guided by Tests" by Steve Freeman and Nat Pryce

There is an abundance of TDD blogs. Many of them make TDD look like requiring hard work simply to be proud of the code coverage later. This book showcases how TDD actually saves time and money.

Downside: Even though I adored the elegance of the test-driven workflow proposed in this book, I wasn't really able to copy the elegance to my NodeJS systems.

Blog Post "Dependency Composition" by Daniel Somerfield

https://martinfowler.com/articles/dependency-composition.html

This blog post showcases Daniel's adoption of dependency injection into the NodeJS world. I love that he does not blindly use javascript classes and their constructors to inject dependency but factory functions instead (factory function is a big word for export const createModule = (dependencies) => async function realFunctionUsingTheDependencies(...) {...}

Blog Post "Clean Architecture is NOT a project structure." by Steve Bishop

https://medium.com/@stevebishop_89684/clean-architecture-is-not-a-project-structure-b158c9c4163f

In NodeJS world, most beginner tutorials use a package-by-layer project structure. There are still enough package-by-module tutorials explaining the benefits of this approach so I don't list a specific one here.

However, although following package-by-module and clean architecture, I only pushed the "Package by Layer" approach into the second level of the architecture. Then, there was src/User/2_infra, src/User/1_app, src/User/0_domain.

In his blog post, Steve explains a more scalable approach.