Creational

Singleton

Type of object that can be instantiated once

In Typescript, just use a global object, so you don't have the boilerplate.

Prototype

Object.getPrototypeOf

Builder

Build object step by step through different methods instead of using many parameters

Factory

Determine which object to instantiate

Structural

Facade

Simplified to hide low-level details of a system

Proxy

Reactivity system of Vue :D

Replace an original object and do some side effects

Advantage: allow user to work with the proxy just like the original object but it can trigger side effects behind the scene.

Proxy are also used when there is a large object that would be expensive to duplicate in memory.

Behavioral

Iterator

Traverse through a collection of objects.

A pull based system.

An object with a next() method in javascript that returns a { done: boolean; value: T }.

Observer

Allow many objects to subscribe to events that are broadcast by another object.

A Subject where other objects subscribe to it and triggers their method when the subject notify

Mediator

In case of many to many relationships, one object is a coordinator between them.

Middlewares are an example of mediator.

State

What is the difference between state and strategy pattern?

A framework for building a web app in Rust 🤔
May be useful someday.

It's true that the Rust ecosystem is growing and tools are coming. But we lack the knowledge of how we can put things together. Here it fills the gap.

One of the reasons that I advocate for SQLite on the server is that I've noticed that servers written on SQLite generally require less maintenance than those written on Postgres. I've also found that servers written in ways that can be deployed as static binaries tend to require less maintenance than those with more complicated deployment setups.

TL;DR SPAs hurt the built-in navigation of the browser. Developers reinvent the wheel for it and it is common to make mistakes bout it.
Some use cases are justified such as Youtube or Soundcloud (keep playing a video while navigating).

A methodology to build software-as-a-service apps

How to sort each type of technologies:

• what we have
• what we want
• what we don't want at all

Using an ARCHITECTURE.md file next to the README and CONTRIBUTING file to make it easy for newcomers to know where the modifications should be made.

Wow I definitely need to read this on my free time !

I can't say this enough.

You will read code more than you write code.

Learn to get good at it.

Principles :

• Incremental improvement
• Reuse what exists (Don't reinvent the wheel principle)
• Five Whys
• Keep it simple stupid (KISS principle)
• Perfect is the enemy of good enough (or make it works, make it right, make it fast)
• Postpone complexity : "premature optimization is the root of all evil" - Donald E. Knuth

Sort the components into :

1. Atoms
2. Molecules
3. Organisms
4. Templates
5. Pages

Bien expliqué :)

Introduction à C4

I put it on the heap for some time or other

Un bon podcast sur les MPA (Multi Page Application) et les SPA (Single Page Application) :)

Un mémo des différentes relations possibles