Andres Cespedes Morales pedes

Code of Conduct

A code of conduct is a set of rules outlining the social norms and rules and responsibilities of, or proper practices for, an individual, party or organization

Summary

The {NAME} is dedicated to providing a harassment-free working environment for all, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of any form. All communication should be appropriate for a professional audience including people of many different backgrounds.

Sexual language and imagery is not appropriate for any communication and/or talks. Be kind and do not insult or put down others. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for {NAME}. Staff violating these rules should be reported to an appropriate line manager.

openssl

Install

Install the OpenSSL on Debian based systems

sudo apt-get install openssl

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

What's an Effective Engineer?

Installing Postgres via Brew

Pre-Reqs

Brew Package Manager

In your command-line run the following commands:

brew doctor
brew update

Rules to write a better commit message

These are my preferences for a good commit message, feel free to fork this gist and add your own standards, or add comment here to share yours with the community.

1. Include only the files related to the feature you are implementing:

Don't add any file that is not related to the main issue, you can make it in a separate commit.
Separating files that not related is important in the revert cases.
Revise the whole changes always before committing and make sure to mention each change you made in the message.

2. Commit subject should be concise and reflect the essence of the commit:

Imagine the commit as an Email to the owner or your team mates.
Subject in the first and main sentence of the commit, it should be concise and to the point.
It shouldn't exceed 50 char.

Command	Description
`uname -a`	Shows the current kernel and OS information
`sudo`	Executes the command as root (Administrator)

Performance Benchmark test for Mule App over HTTPS

Specs

Simple PUT request with a JSON payload with 2 strings
1 Flow
HTTPS with p12 Keystore using a RSA public certificate 2048 bits key
Running on MacBook Pro (16-inch, 2019), 2,4 GHz 8-Core Intel Core i9, 64 GB 2667 MHz DDR4
Java 8 openjdk version 1.8.0_312
Using ab apache benchmark, more details at https://httpd.apache.org/docs/2.4/programs/ab.html
data: ```{

	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD

	#!/bin/bash

	# Thanks goes to @pete-otaqui for the initial gist:
	# https://gist.github.com/pete-otaqui/4188238
	#
	# Original version modified by Marek Suscak
	#
	# works with a file called VERSION in the current directory,
	# the contents of which should be a semantic version number
	# such as "1.2.3" or even "1.2.3-beta+001.ab"

	// Comment for DW, how to extract the original HTTP error using until succesful

	{
	statusCode: error.exception.cause.cause.cause.errorMessage.attributes.statusCode,
	reason: error.exception.cause.cause.cause.errorMessage.attributes.reasonPhrase,
	message: error.exception.cause.cause.cause.errorMessage.typedValue,
	service: error.exception.cause.cause.cause.detailMessage
	}