This is the 47th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 46th Step, read it.
As you can see from the picture, we can deduce well what goes inside a typical programmer. It may seem we know everything and it’s under our control. In actual we may have a vague picture of what we really ought to be doing.
What is a commit?
If you are new to version control, particular to git, than commit might be a new term.
Commit in git stores the current contents of the index in a new commit along with a log message from the user describing the changes.
Why know your next commit?
We should know our next commit, because that would give us a clear understanding of the problem we are working on.
If we don’t know our next commit, we need to analyze the task at hand at detail first. This includes understanding what story are you working on and the context in which we should be fixing or adding stuff to solve it.
TL;DR Don’t work just because the story seems solvable. First understand the problem more deeply and try to solve it in steps.
Go to 46th Step
Go to the 48th path
References:
- 97 things Every Programmer Should Know ~ Git Book
- 97 Things Every Programmer Should Know ~ Paperback
