search

apatequil / SOLIDPrinciples.TS

0 stars 0 forks source link

Guidance for adhering to SOLID principles? #15

Open nick-extend opened 3 years ago

nick-extend commented 3 years ago

Years ago, I spent some time in Ruby and came across lots of Sandy Metz's work. She has a lot of incredible explanations around good code and practicality.

One thing that I've encountered over and over is the tension that arrives when a class / object starts to break SOLID principles or grows beyond its single responsibility. I'm reminded of The wrong abstraction and how, if we're to aggressive about "clean code", that it can become a burden.

One question of mine would be: when do you decide it's time to abstract?

This could also be outside of the purpose of this repo, so happy to close if so!

apatequil commented 3 years ago

@nick-extend: Totally inside the scope of this repo, great suggestion! Keep em coming! Also you're more than welcome to pick an issue and work it if you were so inclined (no obligation).