A dead stupid (yet effective) git dashboard in 3 lines of bash

 

Fork me on GitHub or just grab the code from the gist.

Preemptive commit comments

tl;dr version

Rule #1: write commit comments before coding
Rule #2: write what the software should be supposed to do, not what you did

Help me, because I think Martin Fowler has a Merge Paranoia

There must be something very wrong with me: for the first time in my life I think that Martin Fowler is wrong on a specific topic. And, since Martin is Martin and I’m just a humble developer (Arialdo who?) I’m likely to be the one who’s completely off the track.Nevertheless, unfortunately, no matter how much I dig into the topic, I’m not able to convince myself that Martin Fowler’s arguments about Feature Branching, Continuous Integration and Feature Toggling are right.

Please, help me to understand what I’m missing.

Advertisement

Perché Martin Fowler non ha capito il Feature Branching

Traduzione dell’articolo Why does Martin Fowler not understand feature branches

git and the Art of Visualizing Information

I’m in love with git, and I’ve been devoting a lot of time and efforts in promoting it in the companies where I used to work.

I always found hard to effectively communicate to TFS, svn and cvs users the paradigm shift that git requires. Depicting information and ideas turned out to be the most successful approach.

Yet, visualizing information is an art.

Event sourcing and git

I attended DDD Day in Bologna, last Saturday. Greg Young was really amazing and effective in introducing Command and Query Responsibility Segregation and Event Sourcing to the audience.