Sujeet Agrahari sujeet-agrahari

GROKKING NOTES

I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.

So below I made a list of leetcode problems that are as close to grokking problems as possible.

Pattern: Sliding Window

`vs` Questions

http://stackoverflow.com/questions/804115 (rebase vs merge).
https://www.atlassian.com/git/tutorials/merging-vs-rebasing (rebase vs merge)
https://www.atlassian.com/git/tutorials/undoing-changes/ (reset vs checkout vs revert)
http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See git rev-parse)
http://stackoverflow.com/questions/292357 (pull vs fetch)
http://stackoverflow.com/questions/39651 (stash vs branch)
http://stackoverflow.com/questions/8358035 (reset vs checkout vs revert)

A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.

Engines and libraries

three.js: JavaScript 3D library
stack.gl: an open software ecosystem for WebGL, built on top of browserify and npm.
PixiJS: Super fast HTML 5 2D rendering engine that uses webGL with canvas fallback
Pex: Pex is a javascript 3d library / engine allowing for seamless development between Plask and WebGL in the browser.
Babylon.js: a complete JavaScript framework for building 3D games with HTML 5 and WebGL
Filament: Filament is a real-time physically based rendering engine for Android, iOS, Windows, Linux, macOS and WASM/WebGL
ClayGL: A WebGL graphic library

execute command as another user

sudo -u <user> bash -c "<command to execute>"

	-- turn off paging (less/more)
	psql> \pset pager off

	/*
	Pager usage is off.
	*/

	-- find an object name by id

	SELECT OID, relname

	WITH table_scans as (
	SELECT relid,
	tables.idx_scan + tables.seq_scan as all_scans,
	( tables.n_tup_ins + tables.n_tup_upd + tables.n_tup_del ) as writes,
	pg_relation_size(relid) as table_size
	FROM pg_stat_user_tables as tables
	),
	all_writes as (
	SELECT sum(writes) as total_writes
	FROM table_scans

	--- PSQL queries which also duplicated from https://github.com/anvk/AwesomePSQLList/blob/master/README.md
	--- some of them taken from https://www.slideshare.net/alexeylesovsky/deep-dive-into-postgresql-statistics-54594192

	-- I'm not an expert in PSQL. Just a developer who is trying to accumulate useful stat queries which could potentially explain problems in your Postgres DB.

	------------
	-- Basics --
	------------

	-- Get indexes of tables

	echo-server-epoll
	echo-server-poll
	talk
	talk.dSYM

	#!/bin/bash

	set -eo pipefail

	export KUBE_NAMESPACE=test
	export REPLICA_COUNT=3

	cat <<EOF \| kubectl apply -f -
	apiVersion: apps/v1beta1
	kind: StatefulSet

	/* *******************************************************************************************
	* THE UPDATED VERSION IS AVAILABLE AT
	* https://github.com/LeCoupa/awesome-cheatsheets
	* ******************************************************************************************* */


	// 0. Synopsis.
	// http://nodejs.org/api/synopsis.html