https://github.com/devengage/forward-project

project example for the Engage Forward training program.
https://github.com/devengage/forward-project

Last synced: 3 months ago
JSON representation

project example for the Engage Forward training program.

• Host: GitHub
• URL: https://github.com/devengage/forward-project
• Owner: DevEngage
• License: mit
• Created: 2016-03-21T21:01:03.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2016-03-21T21:37:32.000Z (over 10 years ago)
• Last Synced: 2025-12-26T09:57:47.229Z (6 months ago)
• Size: 1.95 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# forward-project

project example for the Engage Forward training program.

### Tech used in this project

- Angular 1 & 2

- Webpack (manages assets and versions built)

- Ionic 2

- Node.js

- MongoDB

- Firebase

- Bootstrap & Material Design

- React.js

- RXJS 

- NPM

- TypeScript

- SCSS

- HTML

### Design Patterns used in this project

- Model View Controller (MVC)

- Singletons

- Decorator

- Adapter

- Publish/Subscribe or Observer

- Classes and Abstractions 

### Princlples used in this project

- Don't Repeat Yourself (DRY)

  - aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures. 

- Single Responsibility Princple

  - 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. 

- Separation of Concerns

  - design principle for separating a computer program into distinct sections, such that each section addresses a separate concern. A concern is a set of information that affects the code of a computer program. 

- Minimize Coupling

  - Prevent the amount of dependencies on a module of code.

- Maximize Cohesion

  -  Code that has similar functionality should be found within the same component.

- Embrace Change

  - Software Development is always changing and growing so keep up or be left behind.

### paradigms used

A programming paradigm is a style or “way” of programming. Some languages make it easy to write in some paradigms but not others. 

- Functional 

  -  a style of building the structure and elements of computer programs—that treats computation as the evaluation of mathematical functions and avoids changing-state and mutable data.

- Object-Oriented

  - based on the concept of "objects", which may contain data, in the form of fields, often known as attributes; and code, in the form of procedures, often known as methods.