December 5, 2011 at 18:57Cliffhangers in everyday programming
I love programming, but the feeling that the visible result today may not even be visible is demotivating (it often happens that all day you build auxiliary forests and never compile the code, not to mention seeing it in work).
And although any path begins with the first step, I would like the first step to be taken yesterday.
On this occasion, the idea came to me: what if we borrow a reception from the series - Cliffhangers .
The meaning of the idea is very simple: every day we do not start a new story, but find out how the past intriguing ended.
With regard to programming: every day we re-implement what we started yesterday and prepare the basis for tomorrow.
And thus more or less it turned out to personally solve 2 problems:
1. Motivation (I want to start doing something, at least to see how it works (or because of what it does not work));
2. Time planning (to finish something on time becomes a little easier, because it is aimed not only at a fully prepared feature today, but also on the basis of “intrigue” for tomorrow);
What do you think about this?
And although any path begins with the first step, I would like the first step to be taken yesterday.
On this occasion, the idea came to me: what if we borrow a reception from the series - Cliffhangers .
The meaning of the idea is very simple: every day we do not start a new story, but find out how the past intriguing ended.
With regard to programming: every day we re-implement what we started yesterday and prepare the basis for tomorrow.
And thus more or less it turned out to personally solve 2 problems:
1. Motivation (I want to start doing something, at least to see how it works (or because of what it does not work));
2. Time planning (to finish something on time becomes a little easier, because it is aimed not only at a fully prepared feature today, but also on the basis of “intrigue” for tomorrow);
What do you think about this?