Self signed manifesto

This is a living document as long as I keep being a living person.

DevOps and front end developers adhere to lots of manifestos and extend lots of

self signed certificates to get the job done. So I think it wont hurt to share m

y own mashup on those practices.

I call it a manifesto because it share some things with the ones you may find in

the wild:

Has many points that try to prescribe certain behavior that is assumed to be t

he new right way.

It is idealistic to the point of being almost impossible to practice.

It takes for granted the privilege of the signers without questions.

I call it self signed because, well, I'm the one who signs it and I am not tryin

g to coerce anybody to do it.

It is a remainder to myself and a way to share my wishes for an hypothetical fut

ure in which I grow enough food to feed my kids without being functional to any

atrocity.

We do not have to capture market share because we do not believe in such thing

s.

We do not care about time to market because there is no spoon and no market an

d shaping a better future takes time and nurture.

The quality of what we do is measured by the joy of the few closes that share

it not by massive conformism.

We do not have to solve scalability because we do at human scale.

We do not have to solve discoverability because we know each other.

We do not do what we do to earn a living because life is a gift not something

one has to earn.

Worse is worse and massive worse gets dystopian so we try to do what we think

is better at a scale in which we can take responsibility for our mistakes.

Every resource is a commons. So abusing any resource is abusing life and ourselves.