The pleasure of a commit.
The pleasure of a commit.
Time ago I read about what is the main cause of the success of the Post-it's (tm).
The explanation is about the pleasure associated to the fact of "destroy the Post-it'. This means, to our brain, "Task finished. Another parcel of worry free to be dedicated to new things". And our body, to celebrate it, put an endorphin charge, the most natural drug.
Literally, the same sensation is got every time we do a COMMIT (with git, may be a "PUSH").
Like the sensation is GOOD, our brain say "more, more, endorphin!". And we make all possible to get another good sensation like this.
This sensation is, some times the base of the productivity. Because of this, we treat to divide the tasks of programming into little units that permit at least one daily commit. I like the philosophy behind of Git, because he allows the programmer, administrate his own endorphin dosis. He can, divide the assigned task, for what the team wait a PUSH, into more little tasks, COMMITS.
But the question here is "How do you administrate this?" What is your trick to motivate yourself or your team? (thinking in Configuration Management of course)
How do you manage the sensacion of failure associated to a REVERT?
Good "commits" to All!
Time ago I read about what is the main cause of the success of the Post-it's (tm).
The explanation is about the pleasure associated to the fact of "destroy the Post-it'. This means, to our brain, "Task finished. Another parcel of worry free to be dedicated to new things". And our body, to celebrate it, put an endorphin charge, the most natural drug.
Literally, the same sensation is got every time we do a COMMIT (with git, may be a "PUSH").
Like the sensation is GOOD, our brain say "more, more, endorphin!". And we make all possible to get another good sensation like this.
This sensation is, some times the base of the productivity. Because of this, we treat to divide the tasks of programming into little units that permit at least one daily commit. I like the philosophy behind of Git, because he allows the programmer, administrate his own endorphin dosis. He can, divide the assigned task, for what the team wait a PUSH, into more little tasks, COMMITS.
But the question here is "How do you administrate this?" What is your trick to motivate yourself or your team? (thinking in Configuration Management of course)
How do you manage the sensacion of failure associated to a REVERT?
Good "commits" to All!
CC Marjan Venema
ReplyDeleteThanks Jeroen Wiert Pluimers interesting question indeed. I'd say: just avoid ever having to revert... ;) And when you do have to revert, actually do feel the "failure" so you'll be more resolved to take action to avoid having to in the future.
ReplyDeleteBut this approach leads to a place where experimentation is suppressed.
So perhaps, accept reverts as a fact of life and see them as a learning / experimenting experience.
One of those, or much better in my opinion: a combination of them. Do your experiments on separate branches and don't merge before you know you won't have to revert... Everybody happy!