👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
Interesting, I rarely find the need to use inheritance. I favor composition over inheritance. It's got a much looser coupling.
Classes that are shared between feature or domains can live in libraries or folders inside of a shared grouping folder.
About DRY, I think it's generally being used too much as an excuse without considering it's trade-offs. An abstraction made too early can become very expensive and difficult to undo later in a project's life span.
Lead for JavaScript e2e DX at Microsoft Azure. ex-Architect at MongoDB. ex-Principal Architect Adobe Stack at Cognizant. GDE for #Angular and #WebTechnologies Opinions my own.
Education
The Internet
Pronouns
she/her
Work
Principal JavaScript e2e DX/Dev Tools Lead @Microsoft Azure
Interesting, I rarely find the need to use inheritance. I favor composition over inheritance. It's got a much looser coupling.
Classes that are shared between feature or domains can live in libraries or folders inside of a shared grouping folder.
About DRY, I think it's generally being used too much as an excuse without considering it's trade-offs. An abstraction made too early can become very expensive and difficult to undo later in a project's life span.
"Classes that are shared between feature or domains can live in libraries or folders inside of a shared grouping folder."
That was my point.