When you change the world and no one notices

Source: http://www.collaborativefund.com/blog/when-you-change-the-world-and-no-one-notices/

Big breakthroughs typically follow a seven-step path:

1. First, no one's heard of you.
   
2. Then they've heard of you but think you're nuts.
   
3. Then they understand your product, but think it has no opportunity.
   
4. Then they view your product as a toy.
   
5. Then they see it as an amazing toy.
   
6. Then they start using it.
   
7. Then they couldn't imagine life without it.
   

Technology does not drive change. It is our collective response to the options and opportunities presented by technology that drives change.

- Paul Saffo

Reverse Network Effects

http://www.wired.com/insights/2014/03/reverse-network-effects-todays-social-networks-can-fail-grow-larger/

VimDiff Keyboard Shortcuts:

VIMDiff Keyboard Shortcuts:

do - Get changes from other window into the current window.

dp - Put the changes from current window into the other window.

]c - Jump to the next change.

[c - Jump to the previous change.

Ctrl W + Ctrl W - Switch to the other split window.

create a self-signed SSL certificate for local testing

http://www.akadia.com/services/ssh_test_certificate.html

Ways to revert back a git commit already pushed to remote

http://christoph.ruegg.name/blog/git-howto-revert-a-commit-already-pushed-to-a-remote-reposit.html

Good to read

http://joearms.github.io/2016/03/13/Managing-two-million-webservers.html

Microservices Ending up as a Distributed Monolith

Microservices Ending up as a Distributed Monolith

If a service cannot interact within a system unless all these libraries are available, then Christensen calls this a distributed monolith. Essentially all you have done is spread a monolith over the network paying all the cost of a distributed system but losing a lot of the benefits of the microservices architecture. Some of the benefits lost include the characteristic of polyglot, meaning that you loose the possibility of services adopting the best technologies to solve the specific problem, and organizational and technical decoupling, allowing for a team to evolve technically without first having to convince a central authority.

The alternative for Christensen is contracts and protocols, services should hide all their implementation details only exposing data contracts and network protocols.