26 Feb '16, 2am

#programming #ruby #rails Lectured co-workers about the Single Respinsibility Principle today.

Martin defines a responsibility as a reason to change , and concludes that a class or module should have one, and only one, reason to change. As an example, consider a module that compiles and prints a report. Imagine such a module can be changed for two reasons. First, the content of the report could change. Second, the format of the report could change. These two things change for very different causes; one substantive, and one cosmetic. The single responsibility principle says that these two aspects of the problem are really two separate responsibilities, and should therefore be in separate classes or modules. It would be a bad design to couple two things that change for different reasons at different times. The reason it is important to keep a class focused on a single concern is that it makes the class more robust. Continuing with the foregoing example, if there is a ...

Full article: https://en.m.wikipedia.org/wiki/Single_responsibility_pri...

Tweets

CHULUX Single Serve Coffee Maker: The CHULUX Single Serve Coffee Maker is a small yet simple

CHULUX Single Serve Coffee Maker: The CHULUX Si...

singleservecoffee.com 24 Feb '16, 10am

CHULUX Single Serve Coffee Maker The CHULUX Single Serve Coffee Maker is a small yet simple single cup brewer that works w...

#emb2016 What #IoT thing will you build with th...

nxp.com 24 Feb '16, 7pm

Our single chip system modules are a suite of highly integrated solutions in an unprecedented, ultra-small form factor. Ou...