giovannigando

ArgoCD CheatSheet

ArgoCD CheatSheet
Defining an Application

Alexa Cheats

Commands, questions and easter eggs for Amazon Alexa enabled devices: https://ugotsta.github.io/alexa-cheats/

General

"Alexa, stop."
"Alexa, volume one/six/ten."
"Alexa, turn up/down the bass/treble."
"Alexa, mute."
"Alexa, unmute."
"Alexa, repeat."

`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)

references

cheatsheet & tips

JAVADOC CHEATSHEET

Introduction

The major important thing is the documentation has to be implementation independent and specification concise. Dependencies where ever necessary are allowed to be specified.
Also it is allows HTML tags to be used in between the documentation comments. Pretty much all tags are self explanatory.

Meta Annotations
@author Ex: @author Jane Doe
@version Ex: @version v1.0-alpha

Advanced Formatting in GitHub Markdown

GitHub Flavored Markdown lets you create useful documents in GitHub and GitHub Enterprise using .md files. Like other varieties of markdown, GitHub Markdown tries to be as readable as possible in its raw form, resulting in an intentionally limited set of formatting options. However, these options can feel restrictive when dealing with complex content.

Although GitHub Markdown strips out most HTML tags, here are a few tricks that can give you more flexibility when formatting your documents. These advanced formatting options can make your documents more useable, but they come at the expense of plain text readability, so use with caution.

Frontend Technical Interview Prep

EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.

I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.

Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.

Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca

	docker build -t friendlyname . # Create image using this directory's Dockerfile
	docker run -p 4000:80 friendlyname # Run "friendlyname" mapping port 4000 to 80
	docker run -d -p 4000:80 friendlyname # Same thing, but in detached mode
	docker exec -it [container-id] bash # Enter a running container
	docker ps # See a list of all running containers
	docker stop <hash> # Gracefully stop the specified container
	docker ps -a # See a list of all containers, even the ones not running
	docker kill <hash> # Force shutdown of the specified container
	docker rm <hash> # Remove the specified container from this machine
	docker rm $(docker ps -a -q) # Remove all containers from this machine

	/* *******************************************************************************************
	* GLOBAL OBJECTS > ARRAY
	* https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array
	* ******************************************************************************************* */


	// Global object: properties
	Array.length // Reflects the number of elements in an array

	// Global object: methods

	let regex;

	/* matching a specific string */
	regex = /hello/; // looks for the string between the forward slashes (case-sensitive)... matches "hello", "hello123", "123hello123", "123hello"; doesn't match for "hell0", "Hello"
	regex = /hello/i; // looks for the string between the forward slashes (case-insensitive)... matches "hello", "HelLo", "123HelLO"
	regex = /hello/g; // looks for multiple occurrences of string between the forward slashes...

	/* wildcards */
	regex = /h.llo/; // the "." matches any one character other than a new line character... matches "hello", "hallo" but not "h\nllo"
	regex = /h.llo/; // the "" matches any character(s) zero or more times... matches "hello", "heeeeeello", "hllo", "hwarwareallo"