[1Day-1CS] Design Patterns & Paradigms Cleanup

Introduction

Everything I'm organizing now is based on "CS Major Knowledge Notes for Interview". Actually, I think I should have mentioned it at the beginning of Day 1 CS, but I'm writing it now.

Design Patterns

• Conventions created to solve problems that occurred when designing a program through object interrelationships, etc.

Singleton pattern: utilizing dependency injectors to solve the 1-class 1-stance / module binding issue

Factory Pattern: Parent class provides the big picture and subclasses refine it through inheritance

Strategy Pattern: Leverage encapsulated algorithms by swapping them around inside the context

Observer pattern: observes state changes and communicates changes through methods, etc.

Proxy pattern: acting as an interface to intercept the flow before accessing the target object

Iterator pattern: accessing elements of a collection using an iterator, allowing traversal through a single interface.

ExposureModule pattern: a pattern for creating access controllers

MVC pattern: consists of a Model, View, and Controller, allowing you to develop the components of your application in a compartmentalized manner.

• MVP pattern: Replaces only the Controller with a Presenter

• MVVM pattern: Replaces only Controller with View Model

Programming paradigm

• Declarative vs. Imperative → What is declarative and what is imperative?

• Declarative

  • Functional programming: Stacking pure functions to implement logic

• Imperative

  • Object-oriented programming: express the interaction of objects, leverage object methods

  • Procedure-oriented programming: consists of continuous computation, satisfied by verbatim implementation of code