Skip to content

Instantly share code, notes, and snippets.


Pietro Di Bello xpepper

Block or report user

Report or block xpepper

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
xpepper /
Last active Jan 9, 2019

Experimental Generation of Interpersonal Closeness


Instructions to Subjects Included With Task Slips Packet

This is a study of interpersonal closeness, and your task, which we think will be quite enjoyable, is simply to get close to your partner. We believe that the best way for you to get close to your partner is for you to share with them and for them to share with you. Of course, when we advise you about getting close to your partner, we are giving advice regarding your behavior in this demonstration only, we are not advising you about your behavior outside of this demonstration.

In order to help you get close we've arranged for the two of you to engage in a kind of sharing game. You're sharing time will be for about one hour, after which time we ask you to fill out a questionnaire concerning your experience of getting close to your partner.

xpepper / Demistificare il Machine
Last active Jan 5, 2019
Demistificare il Machine Learning (Paolo Perrotta) - alcune mie note
View Demistificare il Machine

Demistificare il Machine Learning

  • X = Input Data
  • Y = Labels (un umano ha etichettato ciascun esempio)

Es. prenotazioni => pizze vendute: c'è una relazione lineare? Sembra.

Scatter plot diagram

Linear regression

xpepper / 0_Exploring Java 9 by Venkat
Last active Oct 28, 2018
Exploring Java 9 by Venkat Subramaniam
View 0_Exploring Java 9 by Venkat

Java 8 was all about how we change the way we write code.
Java 9 is all about how we package and deploy our code. There are almost no code change.
Java 8 changes how we think to and write code. Java 9 changes how we package code.


You read (as in "readability" or visibility) modules, but you export packages.
public is not the same anymore!

xpepper / Developers Should Abandon
Created Sep 2, 2018
Developers Should Abandon Agile
View Developers Should Abandon

Notes taken while reading Developers Should Abandon Agile by Ron Jeffries.

I believe that developers should detach their thinking from any particular named “Agile” method. Instead, they should turn their attention and learning to ways of doing software development that will work within any of those “Agile” methods. Those development approaches, to me, involve use of practices such as, but not limited to, those of Extreme Programming.

More generally, developers’ work should adhere to the foundational principles that support Agile Software Development, as we had in mind when we wrote the Manifesto.

No matter what framework or method your management thinks they are applying, learn to work this way:

xpepper /
Last active Apr 25, 2019
Thomas Pierrain & Bruno Boucard - How To Distill The Core Domain From Your Legacy App (Live Coding)
xpepper / How to uninstall older versions of JDK on a OSX
Last active Aug 19, 2018
How to uninstall older versions of JDK on a OSX machine
View How to uninstall older versions of JDK on a OSX

How to cleanly uninstall older versions of JDK on a OSX machine

Say you want to remove the JDK 1.8.0_161:

Check that's installed with ls -1 /Library/Java/JavaVirtualMachines

for example:

$ ls -1 /Library/Java/JavaVirtualMachines
xpepper /
Last active Jul 31, 2019
London vs Chicago, Comparative Case Study - Sandro Mancuso and Uncle Bob

My notes on the video series "London vs Chicago TDD styles" by Uncle Bob And Sandro Mancuso

The git repo of the kata is here:

The "starting-point" branch is where both implementations began:

  • The 🇬🇧 "openchat-outside-in" branch captures the tomato by tomato history of the London approach.
  • The 🇺🇸 "openchat-unclebob" branch captures the tomato by tomato history of the Chicago approach.

What I like about Sandro's style 👍

xpepper /
Last active Apr 25, 2019
What are Story Points for Mike Cohn

Taken from

Complexity is a factor in the number of points a product backlog item should be given. But it is not the only factor. The amount of work to be done is a factor. So, too, are risk and uncertainty.

Taken together these represent the effort involved to develop the product backlog item.

Story points are an estimate of the effort involved in doing something. That estimate should be based on a number of factors, including the volume of work, the risk or uncertainty inherent in the work, and the complexity of the work.

xpepper / Forget about Clean Code, let’s embrace Compassionate
Last active Apr 25, 2019
a comment on "Forget about Clean Code, let’s embrace Compassionate Code"
View Forget about Clean Code, let’s embrace Compassionate

l’articolo è interessante e condivisibile.

Clean Code è solo un punto di partenza, e nell’apprenderlo passi da Shu (*) (seguo alla lettera ed imparo a dominare le regole prescritte) ad Ha (provo a rompere le regole ed imparo da quello che succede) fino a Ri (vado oltre le regole, creo nuove regole).

Penso che chi scrive abbia superato Shu e stia andando verso Ha e Ri.

Trovo un po’ sterile prendersela con Uncle Bob, che rimane un ottimo mentore se vuoi imparare e andare oltre Shu. Come tutti i mentori non è perfetto sotto tutti i punti di vista, ma non importa, io non devo farci filosofia, devo imparare le regole e i principi del clean code.

xpepper / The Many Meanings of Event-Driven
Created Jun 13, 2018
My notes on the talk "The Many Meanings of Event-Driven Architecture" by Martin Fowler (GOTO 2017)
View The Many Meanings of Event-Driven

GOTO 2017 • The Many Meanings of Event-Driven Architecture - Martin Fowler

(the video is here, the original talk notes are here)

At least one of those four patterns are in play when you talk about "event-driven" architectures:

  1. Event Notification: components communicating via events
  2. Event-carried State Transfer: allowing components to access data without calling the source
  3. Event Sourcing: using an event log as the primary record for a system
  4. CQRS: having a separate component for updating a store from any readers of the store
You can’t perform that action at this time.