Dileep Kumar dileep8014

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

Map, Reduce & Filter

Map
Reduce
Filter

System Design interview - Frontend

Sections to cover in the design:

General reqs
Who is the customer?
How and why they gonna use it?
Are they all from one country or from all over the world?
What are they using now to solve the problem?
How many customers we are expecting with simultanious interactions?

Change structure of project folder with Git

I have this structure:

 project-folder/
     .git
     wp-admin/
     wp-content/
     wp-includes/

.htaccess

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

Vertical decomposition. Creating cohesive services

One of the biggest misconceptions about services is that a service is an independent deployable unit, i.e., service equals process. With this view, we are defining services according to how components are physically deployed. In our example, since it’s clear that the backend admin runs in its own process/container, we consider it to be a service.

But this definition of a service is wrong. Rather you need to define your services in terms of business capabilities. The deployment aspect of the system doesn’t have to be correlated to how the system has been divided into logical services. For example, a single service might run in different components/processes, and a single component might contain parts of multiple services. Once you start thinking of services in terms of business capabilities rather than deployment units, a whole world of options open.

What are the Admin UI

	{
	"openapi": "3.0.1",
	"info": {
	"title": "IMDb-API",
	"description": "The IMDb-API Documentation. You need a <a href='/Identity/Account/Manage' target='_blank'><code>API Key</code></a> for testing APIs.<br/><a class='link' href='/API'>Back to API Tester</a>",
	"contact": {
	"name": "IMDb-API",
	"url": "https://imdb-api.com"
	},
	"version": "1.8.1"

	// Write debounce, then debounce a scroll event

	function onScrollFunction(arg) {
	console.log('scrolling ' + arg);
	}

	function debounce(fn, wait) {
	let timeout;

	return function(...args) {

	def is_valid_state(state):
	# check if it is a valid solution
	return True

	def get_candidates(state):
	return []

	def search(state, solutions):
	if is_valid_state(state):
	solutions.append(state.copy())