Skip to content

Instantly share code, notes, and snippets.

View xpepper's full-sized avatar
💭
😏

Pietro Di Bello xpepper

💭
😏
View GitHub Profile
@xpepper
xpepper / universal-switcher.md
Created November 24, 2023 07:56 — forked from jthodge/universal-switcher
Show macOS app switcher across all monitors
defaults write com.apple.dock appswitcher-all-displays -bool true && killall Dock
@xpepper
xpepper / semantic-commit-messages.md
Last active March 22, 2022 16:55 — forked from joshbuchea/semantic-commit-messages.md
Semantic Commit Messages

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional, and may contain IDs of the task / user story we are changing the code for (e.g. SELL-123)

Example

@xpepper
xpepper / layers_and_boundaries.rb
Last active September 17, 2021 06:34 — forked from joebew42/layers_and_boundaries.rb
A code-ish description of the example depicted in the chapter 25 ("Layers and Boundaries") of "Clean Architecture" book by Bob Martin
interface GameRulesInputBoundary
void moveSouth()
end
interface GameRulesOutputBoundary
void moveSouthSucceed()
end
class GameRules implements GameRulesInputBoundary
def init(GameRulesOutputBoundary outputBoundary)
@xpepper
xpepper / Java8Pills.md
Created March 4, 2021 16:10 — forked from Vashy/Java8Pills.md
Java 8 pills

Java 8 Pills

Example class

@Value // Lombok annotation.
// Generates all private final fields, an all-args-constructor,
// getters (no setters), toString(), etc...
class User {

Clean-Architecture

Notes, comments and errata on Robert C. Martin's Clean Architecture

Reading the book

The book has 34 chapters, with a maximum of 22 pages (chapter 14). Even while involved as a programmer in a project, it should be possible to read one chapter per day, so you can finish the book in about 2 months.

Errata

Page 15, just before subchapter "The greater value".

Question posted on Twitter

For someone with technical leadership responsibilities in a rapidly scaling product company that’s distributed across multiple time zones, what are the top 3 books you think they should read?

My Three

  1. Flow (Donald G. Reinertsen)
  2. Flow (Mihaly Csikszentmihalyi)
  3. Flow (Nonaka, Toyama, Hirata)

Twitterverse

#!/bin/bash
set -e
set -o pipefail
echo '***Start***'
INSTRUCTION="If you want to deploy, try running the script with 'deploy stage region profile', e.g. 'deploy dev eu-west-1 non-prod'"
if [ $# -eq 0 ]; then
echo "Missing arguments."

What is a Design Pattern?

Every Software Engineer certainly must have to deal with change. Change is a constant in Software Design: adding feature, changing of requirement or bug fixing.

What is a design pattern? In simplest way I can say, it is a general solution for common problems in Software Development. The purpose of design patterns is to help structure your code so it will be flexible and resilient when its changed.

There are 23 common design patterns that are being used by programmers around the world. In this chapter I am going to describe the Observer Pattern.

Introduction to Observer Pattern

Before to start

In JavaScript there is NO concept of Class.

Everything is an Object.

Inheritance between objects is achieved with a mechanism known as Prototypal Inheritance.

We can create Objects and then link them together OLOO (Objects-Linked-to-Other-Objects).

@xpepper
xpepper / Study Path on Microservices.md
Last active April 25, 2019 17:25 — forked from pdincau/readme.md
Study Path on Microservices