__ as a rock (well-built)

Now we are looking on the crossword clue for: __ as a rock (well-built).
it’s A 25 letters crossword puzzle definition.
Next time, try using the search term “__ as a rock (well-built) crossword” or “__ as a rock (well-built) crossword clue” when searching for help with your puzzle on the web. See the possible answers for __ as a rock (well-built) below.

Did you find what you needed?
We hope you did!. If you are still unsure with some definitions, don’t hesitate to search them here with our crossword puzzle solver.

Possible Answers: SOLID.

Last seen on: Newsday.com Crossword – Feb 5 2018

Random information on the term “SOLID”:

The single responsibility principle is a computer programming principle that states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility. Robert C. Martin expresses the principle as, “A class should have only one reason to change.”

The term was introduced by Robert C. Martin in an article by the same name as part of his Principles of Object Oriented Design, made popular by his book Agile Software Development, Principles, Patterns, and Practices. Martin described it as being based on the principle of cohesion, as described by Tom DeMarco in his book Structured Analysis and System Specification, and Meilir Page-Jones in The Practical Guide to Structured Systems Design.

Martin defines a responsibility as a reason to change, and concludes that a class or module should have one, and only one, reason to be changed (i.e. rewritten). 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.

SOLID on Wikipedia