Upgrade to Pro — share decks privately, control downloads, hide ads and more …

S.O.L.I.D. Principles of Object Oriented Resume Design

Aga
March 07, 2018

S.O.L.I.D. Principles of Object Oriented Resume Design

Aga

March 07, 2018
Tweet

More Decks by Aga

Other Decks in Business

Transcript

  1. Single Responsibility Principle A module should be responsible to one,

    and only one, user or stakeholder. @agazaboklicka https://jumpstart.blog
  2. Open/Closed Principle A software artifact should be open for extension

    but closed for modification. @agazaboklicka https://jumpstart.blog
  3. Liskov Substitution Principle @agazaboklicka https://jumpstart.blog What is wanted here is

    something like the following substitution property: If for each object o1 of type S there is an object o2 of type T such that for all programs P defined in terms of T, the behavior of P is unchanged when o1 is substituted for o2 then S is a subtype of T.
  4. Liskov Substitution Principle @agazaboklicka https://jumpstart.blog Derived modules must be usable

    through the base class interface without the need for the user to know the difference.
  5. Interface Segregation Principle No client should be forced to depend

    on methods it does not use. @agazaboklicka https://jumpstart.blog
  6. Dependency Inversion Principle High-level modules should not depend on low-level

    modules. Both should depend on abstractions. @agazaboklicka https://jumpstart.blog
  7. Be a STAR of your resume S I T U

    A T I O N T A S K A C T I O N R E S U L T @agazaboklicka https://jumpstart.blog