Nguyen Minh Son misostack

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Picking the right architecture = Picking the right battles + Managing trade-offs

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

# install
yarn global add @angular/cli
# update
yarn global upgrade @angular/cli
# ng help

# Download
wget url
# Extract .tar.gz
tar vxfz *.tar.gz

nest new heyhey -s -l ts

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

Eg: in your angular project, you should ignore changed and search in built folder "dist". Check the below link for details

In general : Preferences --> Settings --> Workspace --> Search "exclude" --> Add Pattern

	import React, { useState, useEffect } from "react";
	import ReactDOM from "react-dom";
	import useForm from "react-hook-form";
	import Input from "@material-ui/core/Input";
	import Select from "react-select";
	import { Input as StrapInput } from "reactstrap";

	import "./index.css";
	import { TextField } from "@material-ui/core";

	Required experience:
	• +5 years' experience working in Software Development:
	• Solid experience in JavaScript ES6 (import/export of Modules, promise, async wait, callbacks) and TypeScript;
	• Solid experience in using Jest Node.js/React.js unit testing framework.
	• Solid experience in designing & developing RESTful APIs and microservices-based systems;
	• Experience in Agile development environments;
	• Familiar with Front-End frameworks, specifically React.js;
	• Well-versed in writing structured, well-documented, maintainable, and clean code;
	• Good problem-solving and analytical skills;
	• Good understanding of standard Software Engineering processes, Testing, and Agile methodology;