@alonso_isidoro alonsoir

Google dork cheatsheet

Search filters

Filter	Description	Example
allintext	Searches for occurrences of all the keywords given.	`allintext:"keyword"`
intext	Searches for the occurrences of keywords all at once or one at a time.	`intext:"keyword"`
inurl	Searches for a URL matching one of the keywords.	`inurl:"keyword"`
allinurl	Searches for a URL matching all the keywords in the query.	`allinurl:"keyword"`
intitle	Searches for occurrences of keywords in title all or one.	`intitle:"keyword"`

Rough Notes about CQRS and ES

Once upon a time…

I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).

I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).

It seems inevitable to throw Domain Driven Design (DDD) in to the mix.

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

	# Used:
	# nmap -p- --open -T5 -v -n ip -oG allPorts

	# Extract nmap information
	# Run as:
	# extractPorts allPorts
	function extractPorts(){
	ports="$(cat $1 \| grep -oP '\d{1,5}/open' \| awk '{print $1}' FS='/' \| xargs \| tr ' ' ',')"
	ip_address="$(cat $1 \| grep -oP '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}' \| sort -u \| head -n 1)"
	echo -e "\n[*] Extracting information...\n" > extractPorts.tmp

	pragma solidity ^0.4.23;

	contract NumberBetweenZeroAndTen {

	uint256 private secretNumber;
	uint256 public lastPlayed;
	address public owner;

	struct Player {
	address addr;

	# We will create a VM with Debian, and inside it execute Minikube with driver=none
	# This way we avoid using Minikube's VM on Windows or Macos, that has a custom kernel
	# You need to install VirtualBox and Vagrant on your host machine before you continue
	# This works for latest versions on 2021-10-22. It doesn't work using Win+WSL2

	# Use the following repository to download Vagrant boxes definition
	git clone https://github.com/sysdiglabs/falco-workshop.git
	# Use box4 that includes Docker, Kubectl, Minikube and many other tools
	cd box4
	vagrant box update

	### Generic Dockerfile demonstrating good practices


	### Imports

	# Bad-ish, we do not need Ubuntu for this, nor do we want latest if we are using in a build system, predictable is better
	FROM ubuntu:latest

	# Better, using a small image since our app has no dependency on Ubuntu
	FROM alpine:3.3

	Driver:
	-Write the code according to the navigator's specification
	-Listen intently to the navigators instructions
	-Ask questions wherever there is a lack of clarity
	-Offer alternative solutions if you disagree with the navigator
	-Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on
	-Make sure code is clean
	-Own the computer / keyboard
	-Ignore larger issues and focus on the task at hand
	-Trust the navigator - ultimately the navigator has the final say in what is written