Giter Club home page Giter Club logo

ruby-solid-study's Introduction

General Assembly Logo

Ruby SOLID Study

This study introduces you to design principles in Ruby. Design principles are rules-of-thumb that help you make decisions about how to structure your code and design your classes. Good design helps manage complexity, makes code resilient to changing requirements, and makes it less expensive to change.

Prerequisites

Objectives

By the end of this, developers should be able to:

  • Recall each principle in the abbreviation SOLID
  • Recognize "code smells" that suggest refactorings toward SOLID design
  • Refactor code using design heuristics

Instructions

  1. Fork and clone this repository.
  2. Change into the new directory.
  3. Create and checkout a new branch, named response.
  4. Follow the directions given in study.md.
  5. When finished, push to your fork and submit a pull request.

You may wish to refer to FAQs related to forking, cloning, and pull requests.

  1. All content is licensed under a CC­BY­NC­SA 4.0 license.
  2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].

ruby-solid-study's People

Contributors

bengitscode avatar dependabot[bot] avatar jrhorn424 avatar laurenfazah avatar micfin avatar samguergen avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

ruby-solid-study's Issues

Inverted phrasing in discussion of LSP

In study.md, under the heading SOLID, there is a sentence that reads:

For example, things we call "Vehicles" should behave like "Sedans", though the latter may
be more specific.

This phrasing seems to imply that Vehicle inherits behavior from Sedan, or that any Vehicle should be able to do anything that a Sedan can do. I would propose the following phrasing instead:

For example, things we call "Sedans" should behave like "Vehicles", though the former may
be more specific.

This phrasing implies the correct inheritance relationship between Sedan and Vehicle.

Please let me know if my understanding of the Liskov substitution principle here is incorrect.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.