Skip to content

Instantly share code, notes, and snippets.

@beelarr
Last active January 17, 2018 04:21
Show Gist options
  • Save beelarr/6a9910a279d3c2dc8f384abac6cf884d to your computer and use it in GitHub Desktop.
Save beelarr/6a9910a279d3c2dc8f384abac6cf884d to your computer and use it in GitHub Desktop.
SOLID
Single Responsibility Principle - class should have one job
Open Closed Principle - Objects should be OPEN for extension but closed for modification
Liskov Substitution Principle - can a subtype substitute for a base type
-- if S is a subtype of T, then objects of type T may be replaced with objects of type S
Interface Segregation Principle - “many client-specific interfaces are better than one general-purpose interface--no client should be forced to depend on methods it does not use
Dependency Inversion Principle - High-level modules should not depend on low-level modules. Both should depend on abstractions.
/////////////////////////////////////////////
Coding process
Break it down
Start and End Dates
Questions
Get Answers
ERD - Entity Relationship Diagram
Sprint Planning
/////////////////////////////////////////////
SCRUM Methodology
Product Owner
Backlog/Queue
In Progress
Under Review
Done
Tested
Sprints < 30 days
Daily Scrum
what we worked on
we we are going to work on
blockers
Retro
Stop
Keep
Start
User Story
Given
When
Then
//////////////////////////////////////////////
Inheritance - Object take on properties of existing objects. Sub/derived class inherits from a Super/base classes
Encapsulation - Restricts direct access to an objects components/methods
Abstraction - reduces something to the essential characteristics which reduces complexity and increases efficiency
Polymorphism - many forms. Shape class >> Square, Circle ect. Each will have different data and are responsible for it.
-- ie  being able to send the same message to different objects and get different results.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment